Alert Type

SRN - Software Release Notification
Low/NotificationSoftware Release Notification
Low/NotificationSoftware Release Notification

Product Affected

ACX EX MX NFX PTX QFX SRX vSRX running Junos Software

Alert Description

Junos 23.2R2-S7.5 images have been recalled and replaced with 23.2R2-S7.7 on 2026-10-14

Please evaluate the new images. See the attachment for additional fixes included in the new image.

Junos Software Service Release version 23.2R2-S7 is now available for download from the Junos software download site

Download Junos Software Service Release:

  1. Go to Junos Platforms - Download Software page
  2. Input your product in the "Find a Product" search box
  3. From the Type/OS drop-down menu, select Junos SR
  4. From the Version drop-down menu, select your version
  5. Click the Software tab
  6. Select the Install Package as need and follow the prompts

NOTE: Starting on August 30th, 2024, we include PR's severity with each entry. See KB86335 [juniper.net] for the definition of PR's Severity

 

Junos Selective Update (JSU) feasible

Not applicable

Call to Action

For your Review

Solution

Junos Software service Release version 23.2R2-S7 is now available.

23.2R2-S7 - List of Fixed issues

PR NumberSynopsisCategory: SPC3 HW and SW Issues
1922949
Critical		Executing unsupported pfe cli triggers chassis reset on srx5000 series
Product-Group=junos
Severity=Critical		On Junos SRX5000 series platforms with Services Processing Card 3 (SPC3), executing the unsupported operational command "show pfe statistics dma" causes loss of communication between the Packet Forwarding Engine (PFE) and the Routing Engine (RE), triggering a system-wide Flexible PIC Concentrator reset and resulting in a complete traffic outage.
PR NumberSynopsisCategory: ACX L2 related features
1933501
Major		Device remains down after reboot, when "input-vlan-map tag-protocol-id" is configured but "ethernet-switch-profile tag-protocol-id" is deleted
Product-Group=junos
Severity=Major		On all Junos platforms, if an interface is configured with "input-vlan-map tag-protocol-id" and the associated "ethernet-switch-profile tag-protocol-id" is deleted while the VLAN mapping is still active, the system may incorrectly allow the configuration commit. If the device is subsequently rebooted or the chassis is restarted, the device may fail to recover and remain down, resulting in traffic impact.
PR NumberSynopsisCategory: "agentd" software daemon
1919448
Major		Heavy traffic flow causing SWAN agent to disconnect from the clients
Product-Group=junos
Severity=Major		In all Junos and EVO platforms, a gRPC connection between the SWAN (Software Wide Area Network) agent and the device is being closed unexpectedly. While SWAN client/JET(Juniper Extension Toolkit) client is connecting and sending data close to 3K(3000) routes at 8KB Per RPC (Remote Procedure Call) over the connection, they can hit rare race condition which can cause the clients to disconnect.
1929823
Major		The sysd process crashes with error logs upon exceeding its memory limit
Product-Group=junos
Severity=Major		On Junos OS Evolved platforms with telemetry streaming configured, the sysd (System Daemon) process crashes on the backup RE (Routing Engine), and error logs are observed when sysd memory usage continues to grow over time, and the memory limit is exceeded. This issue is observed when the 64-bit sysd consumes more memory than the configured system limit when the device has been running for a long time (typically more than 100 days) in the dual RE scenario.
PR NumberSynopsisCategory: BBE Layer-2 Bitstream Access
1941118
Major		Modifying "inner-vlan-id-swap-ranges" with active L2BSA subscribers causes new login failures
Product-Group=junos
Severity=Major		On Junos MX Broadband Edge (BBE) platforms where Subscriber access management service Layer-2 Bitstream Access (L2BSA) solution is deployed, when "inner-vlan-id-swap-ranges" is modified in the presence of active L2BSA subscribers, free inner-vlan-id count is not calculated correctly, hence subsequent L2BSA login attempts fail and subscribers move to pending state.
PR NumberSynopsisCategory: BBE routing
1922536
Major		Forwarding issues for an access DHCPv6-PD or access-internal DHCPv6-IA route or both may be seen on LNS due to an incorrect route programming of such route on PFE
Product-Group=junos
Severity=Major		Drop of traffic to subscriber DHCPv6 prefixes may be observed on LNS (L2TP network server) if CPE uses IPv6 address obtained via NDRA process as the source address for DHCPv6 negotiation instead of link-local address.
PR NumberSynopsisCategory: BBE Statistics daemon & libraries
1856217
Major		Memory corruption in bbe-statsd due to double free for IP demux lite subscribers
Product-Group=junos
Severity=Major		On Junos MX platforms with bbe-statsd running, there is a rare timing issue that could cause memory corruption in the bbe-statsd process due to a double-free scenario for IP demux lite subscribers. The issue could result in bbe-statsd process crashes. but had no service impact. The bbe-statsd process may crash, but there is no service or network impact.
PR NumberSynopsisCategory: Border Gateway Protocol
1880630
Major		Some BGP sessions remain in the Idle state after all interfaces are deactivated and rollback is issued
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms, after all the interfaces are deactivated and the rolled back, some BGP sessions stay in Idle state. This will impact the traffic.
1915893
Major		The rpd process crash triggered by LLGR stale timer expiry and late reconnection of unconfigured BGP peer on helper node
Product-Group=junos
Severity=Major		On all Junos OS and Junos OS Evolved, when Long-Lived Graceful Restart (LLGR) is configured and a Border Gateway Protocol (BGP) neighbor goes down and reconnects after the LLGR stale timer expires, the Routing Protocol Daemon (rpd) process crashes leading to service disruption.
1935730
Major		BGP session teardown due to incorrect 'prefix-limit maximum exceeded' error when RIB sharding is enabled
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms, when prefix-limit or accepted-prefix-limit is configured under family route-target with rib-sharding, prefix-limit will be incorrectly reported as 'prefix-limit maximum is exceeded'. This causes the BGP session to go down immediately. This occurs because the system incorrectly counts each received route multiple times (once for the main thread and once for each shard)
PR NumberSynopsisCategory: BGP BMP Software
1784332
Major		When BGP rib-sharding is enabled, BMP rib-out route withdraw event is not sent occasionally (timing related)
Product-Group=junos
Severity=Major		On Junos and Junos Evolved platforms, , when BGP rib-sharding is enabled and the route is withdrawn from BGP peer, BMP occasionally (timing related) doesn't send rib-out route withdraw event to BMP station. The route is stuck in delete state forever.
PR NumberSynopsisCategory: MX Platform SW - UI management
1906927
Major		SNMP jnxDomCurrentLaneWarnings OID values are wrong due to other lane values are copied from lane 0
Product-Group=junos
Severity=Major		When a interface supports multiple lanes, the SNMP OID jnxDomCurrentLaneWarnings is incorrectly handled as a single lane, resulting in the value from lane 0 being replicated across all other lanes.
PR NumberSynopsisCategory: Class of Service
1928420
Minor		Incorrect COS scheduler-map gets attached to an AE IFL after GRES or 'cosd' process restart
Product-Group=junos
Severity=Minor		On all Junos MX platforms with line cards (MPC1-11, MS-MPC, LC2101, LC2103, LC480, LC4800, LC4802, LC9600, JNP304-LMIC), when a scheduler-map is attached to an AE (Aggregated Ethernet) IFL (Logical Interface) directly or by 'traffic-control-profile' and when this AE is in 'replicate' mode, upon GRES (Graceful Routing Engine Switchover) or on 'cosd' process restart operation, configured scheduler-map gets removed from this AE IFL and a default (Incorrect) scheduler-map gets attached to it. This causes change in the traffic flow pattern via the COS (Class of Service) queues of the AE IFL and can impact service.
PR NumberSynopsisCategory: QFX Control Plane VXLAN
1921796
Minor		Traffic dropped after priority change in VRRP with EVPN-VxLAN scenario
Product-Group=junos
Severity=Minor		On all Junos and Junos Evolved platforms, in Virtual Router Redundancy Protocol (VRRP) with Ethernet Virtual Private Network - Virtual Extensible Local Area Network (EVPN-VXLAN) scenario, when VRRP priority is changed, the VRRP virtual Media Access Control (MAC) address can remain pinned as a static entry on the remote device. As a result, MAC movement does not occur correctly, and VRRP packets are dropped on the leaf device. This impacts VRRP operation after priority changes.
PR NumberSynopsisCategory: Firewall Filter
1859894
Major		MIB2D stucked at 100% on MX10003
Product-Group=junos
Severity=Major		On all MX platforms, during interface flaps with interface-specific / list filters we may see an error "get_counter_list_async: failed in reading counter names (No such file or directory)" due to internal clean-up missing. Please, note that this error is also seen during the churn. This could result in MIB2D hitting at 100% CPU if error remains consistent. The best way to escape this 100% CPU is to restart MIB2d process as soon as the said error is noticed and keep repeating with same counter name.
1903874
Major		[MX10008] cmd='ls -i /var/etc/filters/filter-define.conf' is logged every 1 second instead of every 30 seconds
Product-Group=junos
Severity=Major		An issue where client sessions were not cleared on a router/switch, leaving stale session data that triggered immediate timeout handling instead of the expected 30?second delay. This caused once?per?second master?data lookups and repeated log entries such as "ls -i /var/etc/filters/filter-define.conf", but had no functional impact.
PR NumberSynopsisCategory: VPWS, L2 CKT, EVPN-VPWS
1811884
Minor		Label corruption is seen in l2circuit redundancy when the primary l2circuit is reachable via the backup
Product-Group=junos
Severity=Minor		On all Junos ACX710/ACX5448 platforms configured with l2circuit (Layer 2 circuit) redundancy where primary l2circuit is reachable via backup l2circuit, when the backup router goes down or restarts traffic loss will be seen for the incoming traffic because of the label swapping.
PR NumberSynopsisCategory: DNX VPLS
1911208
Major		VPLS drop seen post Clear OSPF Neighbors .
Product-Group=junos
Severity=Major		Traffic drop seen in VPLS stream post "clear ospf neighbor" command.
PR NumberSynopsisCategory: Dynamic rendering infrastructure
1915225
Major		cli-pfe does not terminate immediately when user issues Ctrl-C
Product-Group=junos
Severity=Major		A cli-pfe show command may continue to gather data in the background after the user issues a Ctrl-C. Eventually the background command will complete. However, the CPU usage for the cli-pfe process will continue to be high while it is still running.
PR NumberSynopsisCategory: JUNOS Dynamic Profile Configuration Infrastructure
1930036
Major		High memory usage is showing, when we configure unsupported licensing feature
Product-Group=junos
Severity=Major		On all Junos EX and QFX platforms operating in an EVPN (Ethernet Virtual Private Network) environment, this issue occurs when the CLI command 'licensing hourly update' is executed on a device that does not support the licensing feature.
PR NumberSynopsisCategory: EVO linux defects & enhancement requests
1892248
Minor		Junos OS Evolved: A Linux kernel vulnerability in the HID driver allows an attacker to read information from the HID Report buffer (CVE-2024-50302)
Product-Group=junos
Severity=Minor		A Use of Uninitialized Resource in the Linux kernel driver for Human Interface Devices (HID) in Junos OS Evolved allows a local low-privileged attacker to use a malicious input device to read information from the report buffer. This could be used to leak kernel memory, enabling the exploitation of additional vulnerabilities. Please refer to https://supportportal.juniper.net/JSA106000 [juniper.net] for more information.
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1916646
Major		IRB interface state is observed incorrect on IFD events tracked by a Network Isolation group
Product-Group=junos
Severity=Major		On MX, EX9200, QFX, PTX platforms, Traffic forwarded over the IRB (Integrated Routing and Bridging) is impacted when isolation decisions rely on the state of a tracked interface, because the Network Isolation Group tracks the interface but processes only IFL (Interface Logical) events and does not process IFD (Interface Device) events.
1926818
Major		ARP resolution failure for /32 static host routes via IRB in EVPN virtual-switch routing instances
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms that support EVPN (Ethernet VPN) virtual-switch routing instances, ARP (Address Resolution Protocol) resolution fails for static host routes configured with a /32 mask when the next-hop interface is an IRB (Integrated Routing and Bridging) interface and the destination host resides in a different subnet. As a result, ARP entries are not installed, MAC (Media Access Control) addresses of destination hosts are not learned, and traffic destined to those hosts becomes unreachable, causing service impact.
PR NumberSynopsisCategory: EX interfaces issues
1909608
Minor		Auto-negotiation is not displayed in 'show interfaces' command output
Product-Group=junos
Severity=Minor		On EX3400 and EX4400-48F, when using 1G optics, the auto-negotiation information does not appear in the output of the "show interfaces" command.
PR NumberSynopsisCategory: EX4400 PFE software
1894136
Major		Physical Interface device remains down by continuous system reboots on EX and QFX5K platforms
Product-Group=junos
Severity=Major		On Junos EX and QFX5K platforms in a scaled setup having high number of Virtual Chassis members (5 or more VC members) , the physical interface device (IFD) remains down when continuous system reboots are performed (5-6 reboots), thus impacting network availability. This is a rare case scenario.
1908971
Major		DHCP Snooping drops due to misrouted server packets causing intermittent issues.
Product-Group=junos
Severity=Major		Intermittent performance issues observed across sites due to anomalous DHCP behavior, where DHCP server packets are incorrectly received on downstream switch interfaces, triggering snooping drops.
PR NumberSynopsisCategory: EX4400 platform
1932557
Major		Running 'request support information' command may result in disk I/O errors
Product-Group=junos
Severity=Major		On EX4400 platforms, running the command 'request support information' may result in disk I/O errors. This issue occurs because the RSI process runs an internal command that retrieves eMMC details using chipset vendor-specific operations. These commands were originally used during early platform development but can conflict with normal eMMC operations when executed concurrently. This causes service disruption.
PR NumberSynopsisCategory: Enhanced Broadband Edge support for firewall
1928462
Major		FPC crash occurs after configuration changes are made to a service-filter on specific MX platforms
Product-Group=junos
Severity=Major		FPC crash and aftd-trio core-dump will be observed on MX platforms supporting MPC10E, MPC11E, LC9600 line cards, and MX304 after configuration changes were made to a service-filter which was in use by BBE subscribers.
PR NumberSynopsisCategory: SRX1500 platform software
1905001
Minor		FPC stuck in network loop scenario
Product-Group=junos
Severity=Minor		On SRX1500 in network loop scenarios, FPC gets stuck and traffic drop happens. System can be recovered by rebooting the device.
PR NumberSynopsisCategory: LC4800 specific Fabric software issues
1881595
Minor		When an FPC is ungracefully offlined it remains online for 12 minutes causing a service impact
Product-Group=junos
Severity=Minor		On all MX platforms with 2 or more FPCs (Flexible PIC Concentrators), a temporary service impact will be observed if a FPC is ungracefully offlined (for example, due to an ungraceful switchover, command to simulate ungraceful offline, or physical removal). The FPC that is being ungracefully offlined appears online for ~12 minutes before going offline. During this 12-minute period, the Fabric Manager remains in a stuck state and recovers automatically after the FPC goes offline.
PR NumberSynopsisCategory: Integrated Routing & Bridging (IRB) module
1933452
Major		ICMP ping with higher MTU size fails in VPLS when IRB MTU exceeds MPLS core MTU
Product-Group=junos
Severity=Major		On all Junos OS platforms, configured with VPLS (Virtual Private LAN Service) and IRB (Integrated Routing and Bridging ) interfaces, when the MTU (Maximum Transmission Unit) configured on the IRB or CE interface is larger than the MPLS ( Multiprotocol Label Switching ) core interface MTU (including MPLS label overhead), ICMP Echo Request (ping) packets with higher packet sizes fail.
PR NumberSynopsisCategory: jdhcpd daemon
1927449
Major		Jdhcpd cores generated after upgrade
Product-Group=junos
Severity=Major		jdhcpd cores seen after upgrade with dhcpv6 for IANA/PD
PR NumberSynopsisCategory: SRX power-mode (PMI/PME)
1858490
Major		flowd crashes due to a timing issue during IPsec SA re-keying on certain SRX platforms
Product-Group=junos
Severity=Major		On certain SRX platforms, the flowd process crash is observed during Internet Protocol Security (IPsec) Security Association (SA) re-keying. This occurs due to an internal timing issue, leading to IPsec tunnel establishment failure, traffic loss during re-key events, and traffic switchover.
PR NumberSynopsisCategory: IPSEC/IKE Key Management
1922670
Critical		KMD process crash during RG0 failover with ADVPN shortcuts in HA cluster
Product-Group=junos
Severity=Critical		On SRX and MX platforms using the IPsec Key Management Daemon (KMD), RG0 failover or failback while Auto Discovery VPN (ADVPN) shortcuts are active may cause the KMD process to crash, temporarily disrupting ADVPN sessions.
PR NumberSynopsisCategory: l2 flow module
1856200
Major		PFE crash due to invalid cached next hop during reinjection on SRX5k
Product-Group=junos
Severity=Major		On SRX5k devices, the PFE (Packet Forwarding Engine) may suddenly crash with a core dump written and force a restart against all line cards during massive interface or route changes when the system caches and reinjects an invalid next hop.
PR NumberSynopsisCategory: Firewall Network Address Translation
1933239
Critical		The FPC restarts on SRX series platforms when session-persistence-scan is configured
Product-Group=junos
Severity=Critical		On Junos OS SRX Series platforms with 'session-persistence-scan' and NAT46 or NAT64 configured, modification to source Network Address Translation (NAT) rule will cause Flexible PIC Concentrators (FPCs) to restart when there is live IPv6 traffic. This will cause all traffic to be dropped and cause service disruption.
PR NumberSynopsisCategory: IPSEC/IKE VPN
1815800
Minor		Small memory leak in ikemd process when deleting vpn tunnel.
Product-Group=junos
Severity=Minor		Small memory leak in ikemd process when deleting vpn tunnel.
1848834
Major		IKED core might be observed during a restart or failover event.
Product-Group=junos
Severity=Major		When IPSEC (Internet Protocol Security) is enabled, during a restart or failover, a failure in adding a node might occur while attempting to read from the Database. Consequently, when a deactivate operation is performed on the configuration, the system attempts to delete a node that was never successfully added. This mismatch between the system state and the database triggers a core dump.
PR NumberSynopsisCategory: Security platform jweb support
1931780
Major		The Captive Web Authentication might not be completed on specific Junos versions for EX Series switch
Product-Group=junos
Severity=Major		When a MAC-RADIUS authentication succeeds and the RADIUS server returns CWA redirect attributes (URL-Redirect), the EX switch should intercept client HTTP traffic and return an HTTP 302 redirect to the Captive Portal. The switch instead responded with HTTP 405 (Method Not Allowed), causing the client to bypass the CWA redirect workflow.
PR NumberSynopsisCategory: Layer2 forwarding on EX/NFX/PTX/QFX
1816344
Major		EVPN : Traffic failure after multiple link flaps of core facing interfaces on scaled setup
Product-Group=junos
Severity=Major		ARP resolution failure when there is quick flap of core facing interface on scaled setup
1928530
Critical		A buffer overflow during IPv6 NDP operations in an EVPN environment caused segmentation faults leading to FPC crash files and repeated reboots
Product-Group=junos
Severity=Critical		On JunOS MX240/MX480/MX960/MX2008/MX2010/MX2020 platforms with MPC10E/MPC11E line cards as well as the MX304 platform, an issue in IPv6 EVPN (Ethernet Virtual Private Network) during NDP (Neighbor Discovery Protocol) resolicitation of a link local target address causes the system to use the IRB link local address in outgoing packets. Stack corruption happens when handling the IRB link local address and resulting in continuous FPC (Flexible PIC Concentrator) reboots (around 3 or 4 times) and crash files generation.
PR NumberSynopsisCategory: Multiprotocol Label Switching
1923867
Minor		The rpd process crash is observed after a graceful restart in the RSVP-TE scenario
Product-Group=junos
Severity=Minor		On Junos OS and Junos OS Evolved platforms with Graceful Restart and RSVP-TE (Resource Reservation Protocol - Traffic Engineering) configured, an rpd crash is observed, leading to traffic impact after a Graceful Restart if a PVC (Permanent Virtual Circuit) fails to allocate correctly during this recovery process, leaving it in an incomplete or unallocated state, and the system attempts to clean up or remove this unallocated PVC.
PR NumberSynopsisCategory: Express Chip L3 software
1842744
Minor		Incorrect MTU value in the ICMP Next-Hop MTU field, regardless of the actual MTU of the outgoing interfaces
Product-Group=junos
Severity=Minor		On Junos PTX and QFX1000X platforms, when destination address is reachable through indirect/unilist next-hop and the MTU size of the outgoing interface is lesser than the packet size, then DUT (Device Under Test) will send the ICMP message back to sender with wrong MTU.
PR NumberSynopsisCategory: Periodic Packet Management Daemon
1909719
Critical		Junos and Junos OS Evolved platforms experience high CPU after FPC reboot causing unpredictable issues with protocols (OSPF/ISIS/BGP, etc.) managed by PPMD
Product-Group=junos
Severity=Critical		After upgrading or rebooting Junos/Junos OS Evolved platforms, a CPU spike may be observed in the PPMD (Periodic Packet Management Daemon) process due to repeated internal message failures. This can lead to BFD (Bidirectional Forwarding Detection) authentication failures. Additionally, other protocols that rely on authentication and PPMD for packet distribution may also be affected, potentially resulting in traffic loss.
PR NumberSynopsisCategory: PTX10K Routing Engine
1870082
Critical		Image validation fails during the Junos VM validation
Product-Group=junos
Severity=Critical		On all Junos platforms that use pkgs/junos-vmguest/mtx/vmhost-pkg-support when loading image to 25.3+, image validation fails.
PR NumberSynopsisCategory: QFX PFE Class of Services
1894833
Minor		PFE crash observed during VXLAN classifier unbind or EZ-LAG commit operations
Product-Group=junos
Severity=Minor		On Junos QFX5k platforms, a PFE (Packet Forwarding Engine) crash is observed when unbinding VXLAN (Virtual Extensible LAN) access ports or classifiers with large number of SVP (Source Virtual Port) associations, or after committing EZ-LAG (Easy EVPN LAG) configurations with large VLAN-ID list leading to excessive CPU utilization, watchdog timeout, and eventually a crash.
PR NumberSynopsisCategory: QFX5K hostpath
1921455
Major		The dcpfe process crashes when adding or removing classifier configuration on QFX5210
Product-Group=junos
Severity=Major		On QFX5210 platform with Class of Service (CoS), the dcpfe process crashes when classifier is configured or removed on interface with active traffic. This can affect traffic forwarding till dcpfe process restarts post crash.
PR NumberSynopsisCategory: for all ipv6 related issues
1922278
Major		IPV6 auto negotiation Router Advertisement packet is missed over configured L2 circuit
Product-Group=junos
Severity=Major		On Junos OS QFX5120 and EX4650, when a L2 circuit is configured between two Customer Premises Equipment (CPE) , IPv6 Router Advertisement packets will not be sent to peer. This will cause devices to not exchange IPv6 messages so they cannot automatically be configured with an IPv6 address, therefore IPv6 connectivity won't be established.
PR NumberSynopsisCategory: QFX L2 PFE
1938291
Major		Deactivating sub-interfaces on flexible ethernet ports leads to VLAN traffic loss
Product-Group=junos
Severity=Major		On Junos platforms having QFX and EX, VLAN(Virtual Local Area Network) traffic loss occur on interfaces configured with flexible-vlan-tagging when an L3 (SP style) sub-interface is deactivated on a port that also carries L2 (enterprise style) VLAN units.
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1905607
Major		Hardware MTU stuck at default value, causing packet drops on VXLAN Interfaces
Product-Group=junos
Severity=Major		On QFX5K and EX4K platforms which are running Junos release, when new VxLAN (Virtual Extensible LAN) vlans with IRBs (Integrated Routing & Bridging) are added, the L3 (Layer 3) interface values overwrite the MTU (Maximum Transmission Unit) entries previously programmed for non-VxLAN vlans that use the same hardware token internally. The VxLAN L3 interface is created with default MTU (1514) because L3 interface MTU value is still 1514 as it is not update by RE (Routing Engine).
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1933698
Major		PFE crash due to memory corruption in EVPN-VxLAN type5 overlay ECMP at high tunnel next hop scale
Product-Group=junosvae
Severity=Major		On Junos QFX5110, QFX5120, EX4650, EX4400, EX4100, and EX5200 platforms, when operating with EVPN-VxLAN type5 overlay ECMP at high tunnel next hop scale, the Packet Forwarding Engine (PFE) crash when a memory corruption issue is observed due to a buffer overflow that leads to corruption of heap management structures. This corrupted metadata is detected by the memory manager when later heap allocation or free operations are invoked, resulting in a reported heap corruption condition.
1939298
Major		Traffic drop is seen due to tagged IRB L3 interface with native-vlan and vlan members
Product-Group=junos
Severity=Major		On all Junos OS QFX5K and EX4k platforms, configuring a native VLAN along with VLAN members on an underlay Integrated Routing and Bridging (IRB) Network-to-Network Interface (NNI) that carries VxLAN (Virtual Extensible LAN) traffic results in the VLAN tag not being stripped as expected. Instead of treating the native VLAN traffic as untagged, the interface adds the VLAN tag, leading to packet drops at the remote end.
PR NumberSynopsisCategory: QFX5K JUNOS Interface, MACSec, Optics, SDK, PHY
1938876
Major		Incorrect interface mode leading to 100G Link Flaps on QFX5210-64C
Product-Group=junos
Severity=Major		On Junos OS QFX5210-64C platform, 100G optics inherently operate in CAUI-4 (Chip-to-Module 100 Gb/s Four-Lane Attachment Unit Interface) mode, which is automatically selected by the system and not user-configurable; mismatches due to software versions leading to link instability or flapping.
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platfom issues
1796218
Major		The 100G VCP will go down upon restarting or upgrading the device
Product-Group=junos
Severity=Major		On Junos QFX5K platforms in a Virtual Chassis scenario, the 100G VCP (Virtual Chassis Port) will go down and remain in a down state after a device or VCP restart or device upgrade.
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1815837
Minor		Configure low file size in traceoptions while logging volume is high will lead to high CPU and RPD scheduler slips causing operational impact
Product-Group=junos
Severity=Minor		If the file size is too small and the amount of traceoptions volume is too high it can cause scheduler slips and operational impact.
PR NumberSynopsisCategory: RPD API infrastructure
1715599
Critical		Inconsistent RPD crash found in rt_walk, task_job_run_job_bg, task_scheduler
Product-Group=junos
Severity=Critical		PRPD installed flowspec routes were not deleted on routing-instance delete, leading to RPD crash.
PR NumberSynopsisCategory: SRX branch platforms
1889549
Major		The XE interfaces of SRX380 platform with 1G SFP (fiber) are flapping continuously when LACP is enabled
Product-Group=junos
Severity=Major		When LACP (Link Aggregation Control Protocol) is enabled using 1G SFP(Small Form-factor Pluggable)-fiber (such as SFP-SX, SFP-LX etc) over XE interfaces, frequent state transitions will repeatedly trigger configuration updates. Due to LACP instability, the interfaces will continuously flap. As a result, the port configuration will be re-applied automatically which leads to a loop of re-configurations until the LACP state stabilizes.
1913911
Major		ARP reply packets may be sent out from the STP blocked port
Product-Group=junos
Severity=Major		On SRX300-series devices, when ethernet-switching is used with spanning-tree protocol enabled, in some cases ARP reply packets may be sent out from a spanning-tree blocked port.
1927646
Minor		Ethernet interfaces with fiber SFPs and configured with 'family ethernet-switching' and 'no auto negotiation' don't come up after reboot
Product-Group=junos
Severity=Minor		After reboot on branch SRX300 Series platforms, interfaces using Small Formfactor Pluggable (SFP) SX/LX fiber transceivers and configured with 'family ethernet-switching' and 'no auto negotiation' might remain in a down state due to incorrect physical medium detection by the Ethernet physical layer (PHY). The issue is timing-dependent, it might happen with single or after several reboots.
PR NumberSynopsisCategory: Trio pfe l3 forwarding issues
1922741
Minor		FPC heap memory will be leaked when CCNHs are recreated due to VPLS PNH are getting deleted and re-added
Product-Group=junos
Severity=Minor		On Junos MX platforms with MPC1-9/LC480/LC2101 (including MX204 and MX10003 platforms) when "set protocols l2circuit resolution preserve-nexthop-hierarchy" is enabled, FPC heap memory will leak when CCNHs (Chained Composite Next Hops) are recreated because of the VPLS (Virtual Private LAN Service) PNH (Preserve Nexthop Hierarchy) are getting deleted and re-added.
1927194
Major		When a resolution for an IPv4/IPv6 address fails, NH IFL is throttled causing service impact
Product-Group=junos
Severity=Major		In MX uKern and AFT based cards, NH IFL throttling will be seen when resolution for an destination IPv4/IPv6 address fails.
PR NumberSynopsisCategory: DDos Support on MX
1801213
Major		DDOS protection Max arrival rate shows incorrect values
Product-Group=junos
Severity=Major		On MX platforms with MPC10/MPC11/LC9600 and MX304 platforms, DDOS max-arrival rate value is incorrect in "show ddos-protection protocols" command.
PR NumberSynopsisCategory: Configuration management, ffp, load action
1854461
Major		Configured TFTP server connection and rate limits are not applied
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms configured as Trivial File Transfer Protocol (TFTP) server , "connection-limit" or "rate-limit" values are not updated as per configured values.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1947196
Minor		Commitd core dumps observed during specific config commits with "patch generation error - not syncing patch"
Product-Group=junos
Severity=Minor		Resolved an issue where configuration commits could intermittently fail when applying certain routing policy changes. The problem occurred only under specific conditions during commit processing and could result in the commit operation aborting unexpectedly. This fix improves commit stability when updating routing policies.
PR NumberSynopsisCategory: Issues related to NETCONF
1906621
Major		RPC reply delayed for commit during NETCONF over SSH session on Junos TVP-based VMhost platforms
Product-Group=junos
Severity=Major		On JUNOS VM Host-based platforms, when performing NetConf "", an internal script caused its PID to be displayed in the NETCONF session during commit.
PR NumberSynopsisCategory: content filtering bugs
1927484
Critical		Traffic loss occurs due to high memory utilisation in UTM pools
Product-Group=junos
Severity=Critical		On Junos OS SRX platforms, configuring cache preload in web filtering causes high memory utilization in the UTM (Unified Threat Management) pool, which results in traffic loss.
PR NumberSynopsisCategory: VMHOST platforms software
1927342
Minor		Junos VMhost platforms restart unexpectedly due to deadlock
Product-Group=junosvae
Severity=Minor		On all Junos VMhost platforms, when Junos performs disk access, a rare deadlock involving FreeBSD kernel processes will occur. This condition causes FreeBSD kernel panic, resulting in crash of vmcore and an unexpected device restart, leading to temporary system unavailability.
PR NumberSynopsisCategory: Virtual Private LAN Services
1806424
Major		The snmp mib walk on jnxVplsPwBindTable fails with vpls routing-instances having multiple mesh-groups
Product-Group=junos
Severity=Major		If VPLS mesh-groups are configured with different neighbours having different vpls-id the SNMP mib walk over jnxVplsPwBindTable might fail with the error Request failed: OID not increasing. No functional impact is seen due to this issue.
PR NumberSynopsisCategory: usf ams related issues
1913560
Major		Routing Engine restart on MX platforms with SPC3 line card could cause loss of traffic processing
Product-Group=junos
Severity=Major		On Junos MX960, MX240, and MX480 platforms using SPC3 service line cards, restarting the Routing Engine may result in the network security daemon (nsd) not starting or failing to program internal subsystems like service sets . When this occurs, the control plane becomes unavailable and traffic stops forwarding permanently. This is a timing related behavior observed during the boot sequence and does not appear on every restart.
PR NumberSynopsisCategory: usf flow and datapath issue on SPC3
1925039
Major		Memory leak in ipv4-to-ipv6 session reuse trigger flowd crash
Product-Group=junos
Severity=Major		On Junos OS MX240/MX480/MX960 platforms with MX-SPC3 cards, the flowd process crash and reboots the service PIC when a stale IPv4 session is mistakenly reused for IPv6 due to a memory issue. During process restart the services remain down, session information is briefly lost and active traffic will drop, however the system recovers automatically.
PR NumberSynopsisCategory: usf nat related issues
1881192
Major		NAT Pool Installation failure due to Service-Set name length mismatch
Product-Group=junos
Severity=Major		On MX240, MX480, and MX960 platforms with SPC3 ( Services Processing Card 3 ) , new NAT ( Network Address Translation ) pools may fail to install, this is due to a mismatch in service-set name length handling. The system stores only 32 characters for service-set information, causing failures when names exceed this limit.

 

Extended Solution

23.2R2-S7 - List of Known issues

PR NumberSynopsisCategory: EX4300 Mutlicast implementation
1873129
Major		The PTP packets are dropped when IGMP snooping is enabled
Product-Group=junosvae		On EX4400, EX4100, QFX5120 and EX4650 platforms running Junos Operation System (OS), when Internet Group Management Protocol (IGMP) snooping is enabled on Virtual Extensible Local Area Network (VXLAN) Virtual Local Area Network (VLAN), all unknown multicast packets will be dropped. As a result, PTP (Precision Time Protocol) packets that use reserved multicast addresses are also discarded affecting the synchronization of the device with the clock server.

Resolved In: junos:22.4R3-S11 junos:22.4R3-S9 junos:23.2R2-S6 junos:23.4R2-S6 junos:23.4R2-S8 junos:24.2R2-S3 junos:24.2R2-S4 junos:24.4R2 junos:24.4R2-S1 junos:25.2R2 junos:25.2R2-S1 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: SRX Fleming Platforms related issues
1927758
Critical		HA failover not triggered after PFE process crash in HA deployments (Chassis Cluster / MNHA) on SRX1600/2300/4300/4700
Product-Group=junosvae		On SRX1600/2300/4300/4700 platforms configured in HA mode (Chassis Cluster or MNHA), when a PFE (Packet Forwarding Engine) process crash occurs on the active node, HA failover is not triggered because the failure condition is not detected by the HA subsystem. This can lead to traffic disruption and service outage.

Resolved In: junos:23.4R2-S8 junos:24.2R2-S5 junos:24.2R2-S6 junos:24.4R2-S4 junos:25.2R2 junos:25.2R2-S2 junos:25.4R1-S1 junos:25.4R2 junos:26.1R1 junos:26.2R1
PR NumberSynopsisCategory: "agentd" software daemon
1885622
Major		The aaasd process stops responding for RPC calls
Product-Group=junos		On all Junos and Junos Evolved platforms with gRPC configured, the aaasd process rejects incoming RPCs. This issue occurs in some rare cases, and aaasd will stop listening for authentication requests from reverse proxy. This issue does not cause a traffic impact.

Resolved In: evo:22.3X80-D49-EVO evo:24.2R2-S4-EVO evo:24.4R2-S3-EVO evo:24.4X200-D10-EVO evo:24.4X200-D20-EVO evo:25.2R1-S1-EVO evo:25.2R2-EVO junos:24.2R2-S4 junos:24.2X1 junos:24.4R2-S3 junos:25.2R1-S1 junos:25.2R2
1913260
Major		Discrepancy noticed in the interfaces when there is a reset in Linecard or PFE
Product-Group=junos		On all Junos and Junos Evolved platforms, with an established telemetry session with multiple collectors, there will be interface statistics discrepancy when there is a linecard OIR event or PFE offline/online sequence.

Resolved In: evo:22.3X80-D47-EVO evo:22.3X80-D49-EVO evo:23.4R2-S8-EVO evo:26.1R1-EVO junos:23.4R2-S8 junos:24.2R2-S5 junos:24.4R2-S4 junos:25.4R2 junos:26.1R1 junos:26.2R1
1923848
Major		Junos Evolved platfrom, when gNMI collecting data from "optics/lanediags/lane/lane_laser_receiver_power_dbm" and "optics/lanediags/lane/lane_laser_output_power_dbm" are unreadable
Product-Group=junos		The JavaScript Object Notation (JSON) encoding of leafs of type "ieeefloat32"(https://github.com/openconfig/public/blob/master/release/models/types/openconfig-types.yang#L127) is not correct, causing gRPC Network Management Interface (gNMI) data outputs unreadable.

Resolved In: evo:22.3X80-D49-EVO evo:24.4R2-S4-EVO evo:25.4R2-EVO evo:26.2R1-EVO junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: Border Gateway Protocol
1854194
Major		Handling cores when always-compare-med is configured in BGP path selection
Product-Group=junos		When using rib-groups, which copy inet.3 routes to inet.0 and inet6.3, configuring path-selection always-compare-med triggers a local RIB evaluation that will miss inet6.3 because inet6.3 tables are not initialized as a BGP RIB. As a result, Inet6.3 routes will not get updated.

Resolved In: evo:23.4R2-S8-EVO evo:24.4R2-EVO evo:25.1R1-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:22.4R3-S7-J1 junos:23.4R2-S8 junos:24.4R2 junos:25.1R1 junos:25.2R1 junos:25.3R1
1877111
Major		The Aggregate-Bandwidth feature inconsistency on BGP Route Reflectors with VRF L3VPN Multipath
Product-Group=junos		On all Junos and Junos Evolved platforms, the aggregate-bandwidth feature does not function as expected with the device configured as a BGP (Border Gateway Protocol) Route Reflector (RR). This issue is observed specifically in scenarios involving BGP multipath bandwidth aggregation for routes originating from VRF (Virtual Routing and Forwarding) instances under the L3VPN (Layer 3 Virtual Private Network) address family.

Resolved In: evo:23.4X100-D40-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:23.4R2-S8 junos:24.2R2-S2 junos:24.4R2 junos:25.2R1 junos:25.2R2 junos:25.3R1
PR NumberSynopsisCategory: MX304 Routing Engine issues
1913540
Minor		[MX304] Certain 'cat' commands within the 'show vmhost support-info' command in RSI try to access files that are not present on the MX304, causing error messages to appear.
Product-Group=junos		As part of the RSI process, the command "show vmhost support-info" is executed, which comprehensively collects vmhost logs using various cat commands. Some of these commands attempt to access files that do not exist on the MX304, leading to the display of error messages.

Resolved In: junos:24.2R2-S5 junos:25.2R2-S1 junos:25.4R2 junos:26.1R1
1933347
Major		Continuous I/O ata timeout errors and alarms are seen for secondary SSD read accesses
Product-Group=junos		On all Junos platforms with SSD (Solid-State Drive) of Innodisk and model no. is DGM28-B56M71EC1QF-B5531, alarms are observed for secondary SSD along with continuous input/output ata timeout errors for secondary disk read accesses when the SSD firmware is unable to can't handle the continuous metadata reads. No service impact will be seen as the alarms are seen for secondary SSD alone.

Resolved In: evo:26.2R1-EVO junos:24.4R2-S4 junos:25.2R2-S1 junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: MX Platform SW - UI management
1898722
Major		The craft-control process is unable to start on MX10004/MX10008 platforms
Product-Group=junos		On all Junos MX10004 and MX10008 platforms with FPM/craft interface, the craftd (craft control daemon) is unable to run, it causes the craft-control process does not start properly, leading the jnxAlarmRelayMode unable to retrieve data when an alarm condition is triggered. The issue does not cause traffic impact and only may affects monitoring traffic.

Resolved In: junos:24.4R2-S1 junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: L2NG Access Security feature
1911142
Major		Client IP assignment failure observed on EX4300 due to DHCPv6 snooping validation issue
Product-Group=junos		On EX4300, DHCPv6 ( Dynamic Host Configuration Protocol for IPv6 ) clients will fail to receive IP addresses due to improper client entry handling when DHCPv6 snooping is enabled.

Resolved In: junos:21.4R3-S12
PR NumberSynopsisCategory: OpenSSH and related subsystems
1922002
Major		Major alarms showing SPMB1 not online on MX2008 will be seen on 24.2R1 and later releases
Product-Group=junos		On the Junos MX2008 VMhost platform with dual Routing Engines (REs), the backup SPMB {Switch Processor Mezzanine Board} (spmb1) fails to come online following a graceful switchover on releases starting when upgrading to releases starting from Junos 24.1. As a result, if the backup SPMB cannot boot, the traffic will be impacted during switchovers.

Resolved In: junos:24.2R2-S5 junos:24.4R2-S4 junos:25.2R2-S1 junos:25.4R1-S2 junos:25.4R2 junos:26.1R1 junos:26.2R1
PR NumberSynopsisCategory: ACX BFD specific issues
1899540
Major		DNX error logs consuming syslog in ACX platforms post upgrade causing display issue
Product-Group=junos		On Junos ACX710 and ACX5448 platforms, post upgrade the error logs "DNX PKT: (is microbfd pkt) payload length(1) is lesser to have a udp header" are reported in the devices causing display issue.

Resolved In: junos:23.4R2-S7 junos:24.2R2-S4 junos:24.4R2-S3 junos:25.2R2 junos:25.2R2-S1 junos:25.4R2 junos:26.1R1
PR NumberSynopsisCategory: EVPN ELAN/E-TREE
1882561
Major		EVPN-MPLS BUM Traffic Disruption Due to Incorrect QinQ STag Insertion
Product-Group=junos		On Junos OS ACX5448/ACX710 platforms, the traffic towards the MPLS (Multiprotocol Label Switching) core Provider Edge (PE), specifically BUM (Broadcast, Unknown Unicast, and Multicast) traffic, has a QinQ (802.1ad) Service Tag (STag) added to the Customer (CTag). This insertion can disrupt traffic forwarding, leading to malformed packets or corruption of the destination MAC address in the inner Ethernet header.

Resolved In: junos:24.4R2 junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: Host path software for ACX platform
1889637
Major		DHCP clients do not come up when VRF leak and "dhcp-relay" with "no-snoop" are configured under a routing-instance
Product-Group=junos		On all Junos OS Evolved ACX7K Series platforms, when DHCP (Dynamic Host Configuration Protocol) relay mode is used within a routing-instance scenario, DHCP clients fail to come up because DHCP offer packets are being dropped.

Resolved In: evo:23.4R2-S7-EVO evo:24.2R2-S4-EVO evo:24.2R2-S5-EVO evo:24.4R2-S4-EVO evo:25.2R1-S2-EVO evo:25.2R2-EVO evo:25.4R1-EVO evo:26.1R1-EVO junos:25.2R1-S2 junos:25.2R2 junos:25.4R1 junos:26.1R1
PR NumberSynopsisCategory: DNX VPLS
1923586
Major		Benign PFE error log observed during AE bundle disable/enable "pfe_dnx_ifl_get_parent_ifl_ifd_port: failed to get port num for ifd lsi"
Product-Group=junos

Resolved In: junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: Control Plane for Node Virtualization
1908408
Major		Interfaces fail to come up after port speed changes or system power cycle reboot events on MX platforms
Product-Group=junos		On Junos OS MX platforms, after port speed related configuration changes or on MX240, MX480, MX960, and MX10003 platforms in VC (Virtual Chassis) setup, after a powercycle reboot of any VC member, some interfaces which were previously operational fail to return to an operational state due to an internal timing issue during PIC (Physical Interface Card) reinitialization.

Resolved In: evo:25.4R2-EVO evo:26.1R1-EVO junos:23.4R2-S7-J10 junos:23.4R2-S8 junos:23.4R2-S9 junos:24.2R2-S5 junos:25.2R2 junos:25.4R2 junos:26.1R1
PR NumberSynopsisCategory: EVO Netstack Juniper Tunnel Driver Module
1919313
Major		The LDP session does not come up when an IPsec SA is configured under OSPFv3
Product-Group=junos		On Junos Evolved platforms, when Open Shortest Path First version 3 (OSPFv3) Internet Protocol Security (IPsec) SA is applied at the interface (IFD/IFL) level, Label Distribution Protocol (LDP) is able to discover the neighbor via User Datagram Protocol (UDP) Hellos, but fails to bring up the Transmission Control Protocol (TCP) session, preventing the LDP session from becoming operational. Disabling the OSPFv3 IPsec SA immediately restores normal LDP operation. During the service impact, the session will be down and traffic will not be send. Once the LDP session comes up, traffic can be routed through it.

Resolved In: evo:23.2R2-S7-EVO evo:23.4R2-S8-EVO evo:24.2R2-S5-EVO evo:24.4R2-S4-EVO evo:25.2R2-S1-EVO evo:25.4R2-EVO evo:26.1R1-EVO evo:26.2R1-EVO
PR NumberSynopsisCategory: EVPN control plane issues
1821582
Major		Deactivating protocol evpn in a routing-instance configured with 'vrf-target auto' leads to the rpd crash on both REs
Product-Group=junos		On all MX platforms the deactivation a routing-instance configured with 'vrf-target auto' while also configured with protocol evpn (Ethernet Virtual Private Network) leads to the rpd crash in all the REs (Routing Engine) present in the chassis

Resolved In: evo:24.4R1-EVO evo:25.1R1-EVO junos:24.2R2-S3 junos:24.4R1 junos:25.1R1
1862755
Critical		The associated EVPN RI peers are not learning routes when there is change in EVPN RI name or EVPN RI is deleted and added back
Product-Group=junos		On all Junos and Junos OS Evolved platforms with Dual RE with NSR enabled, if automatic RD (Route-Distinguisher) is used for EVPN (Ethernet VPN) RI (Routing Instances) in a scaled configuration setup, and when there is a change in the EVPN RI or the EVPN RI is deleted and added back, the associated EVPN RI remote peers are not learning routes, which results in traffic loss.

Resolved In: evo:24.2R2-S4-EVO evo:24.4R2-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:24.4R2 junos:24.4R2-S2 junos:25.2R1-S2 junos:25.2R2 junos:25.3R1
1924472
Minor		EVPN all-active not working in multi-homed setup when router-id not explicitly configured
Product-Group=junos		On Junos OS and Junos OS Evolved platforms, if the router-id is not explicitly configured, the device dynamically selects a router-id during bootup. In this scenario, the device advertises EVPN (Ethernet Virtual Private Network) Type1 AD/ESI (AutoDiscovery/Ethernet Segment Identifier) and Type4 ES RT (Ethernet Segment Route Target) routes with a Route Distinguisher (RD) of 0:0. As a result, Route Targets (RTs) advertised by different Provider Edge (PE) routers end up having identical prefixes. Consequently, only one PE routers RT is advertised and learned. This behavior prevents EVPN all-active redundancy resulting in the loss of multihoming.

Resolved In: evo:26.3R1-EVO
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1802464
Major		VXLAN/EVPN ip-address for mac-address in forwarding table in hold state
Product-Group=junos		Once receiving the same route as Type 2 and Type 5, the address entry might be stuck in hold state once remote peer restarts. The recovery is simply to clear the mac-ip table on the remote side with 'clear ethernet-switching mac-ip-table or bounce the BGP peer. This race condition is corrected.

Resolved In: evo:22.2R3-S4-EVO evo:22.4R3-S3-EVO evo:23.4R2-EVO evo:24.2R1-EVO evo:24.2R2-EVO evo:24.3R1-EVO junos:21.4R3-S8 junos:22.2R3-S4 junos:22.4R3-S3 junos:23.4R2 junos:24.2R1 junos:24.2R2 junos:24.3R1
PR NumberSynopsisCategory: EX interfaces issues
1904884
Major		VCP link flap due to SYSPLD read failures
Product-Group=junos		On EX4100 platform VCP link flap due to SYSPLD read failures and mark SFP as unplugged

Resolved In: junos:23.4R2-S8 junos:24.2R2-S5 junos:24.4R2-S4 junos:25.2R2-S1 junos:25.4R1-S2 junos:25.4R2 junos:26.2R1
1909608
Minor		Auto-negotiation is not displayed in 'show interfaces' command output
Product-Group=junosvae		On EX3400 and EX4400-48F, when using 1G optics, the auto-negotiation information does not appear in the output of the "show interfaces" command.

Resolved In: junos:23.2R2-S7 junos:24.2R2-S4 junos:24.4R2-S3 junos:25.4R1 junos:25.4R2 junos:26.1R1
1923212
Major		EX4400-24x: fxpc core dump during PHY firmware broadcast download on power cycle @plp_miura_reg_wr_task
Product-Group=junos		On EX4400-24X platform, PFE process (`fxpc`) may crash with a segmentation fault (SIGSEGV) during device boot-up. The crash occurs during the Broadcom PHY (BCM82756/Miura) firmware broadcast download sequence when initializing the external PHY.

Resolved In:
PR NumberSynopsisCategory: EX4400 PFE software
1900891
Critical		Junos OS: EX Series, QFX Series: If the same egress filter is configured on both an IRB and a physical interface one of those is not applied (CVE-2026-33773)
Product-Group=junos		An Incorrect Initialization of Resource vulnerability in the packet forwarding engine (pfe) of Juniper Networks Junos OS on specific EX Series and QFX Series device allows an unauthenticated, network-based attacker to cause an integrity impact to downstream networks.. Please refer to https://supportportal.juniper.net/JSA107815 [juniper.net] for more details.

Resolved In: junos:23.4R2-S7 junos:24.2R2-S4 junos:24.4R2-S2 junos:24.4R2-S3 junos:25.2R2 junos:25.4R1 junos:25.4R2 junos:26.1R1
PR NumberSynopsisCategory: EX POE
1930080
Minor		PoE outage observed on EX4400 in a rare scenario
Product-Group=junos		On EX4400 platforms, loss of PoE (Power over Ethernet) power is seen on ports after port bounce or even during normal operation without specific external trigger . This causes outage on all PoE ports and devices connected to PoE port will not receive power causing service impact.

Resolved In: evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:23.4R2-S8 junos:24.2R2-S5 junos:24.4R2-S4 junos:25.2R2-S1 junos:25.4R1-S2 junos:25.4R2 junos:26.1R1 junos:26.2R1
PR NumberSynopsisCategory: EX Entry Level Access VC platform
1919727
Minor		The dcpfe process crashes repeatedly with continuous error logs 'smb_transfer: SMBus ioctl failed'
Product-Group=junos		On EX4400 platforms, due to an internal communication issue within the CPU controller, the system triggers repeated fxpc panics which in turn lead to the dcpfe process (Dataplane Packet Forwarding Engine) to crash and restart continuously, resulting in service disruption.

Resolved In: junos:23.4R2-S8 junos:24.2R2-S5 junos:24.4R2-S4 junos:25.2R2-S1 junos:25.4R1-S2 junos:25.4R2 junos:26.1R1 junos:26.2R1
PR NumberSynopsisCategory: FIPS related issues
1905490
Major		On MX10003 with FIPS enabled, KATs failure in SMIC_QSFP28_MACSEC_TIC causes system halt
Product-Group=junos		In Junos, MX10003 platforms with Federal Information Processing Standards (FIPS) enabled experience repeated halts due to Known Answer Test (KATs) failures in the SMIC_QSFP28_MACSEC_TIC crypto path.

Resolved In: junos:24.2R2-S5 junos:24.4R2-S4 junos:25.2R2-S1 junos:25.4R2 junos:26.1R1 junos:26.2R1
PR NumberSynopsisCategory: Juniper Device Manager VM Mgmt and infrastructure function
1675919
Critical		NFX350 :: JDI_REGRESSION:PLATFORM:SWITCHING:JDM:: Core "localhost.libvirtMib_suba.15909.1656455866.core.tgz" is seen on NFX-350 boxes
Product-Group=junos		NFX350 :: JDI_REGRESSION:PLATFORM:SWITCHING:JDM:: Core "localhost.libvirtMib_suba.15909.1656455866.core.tgz" is seen on NFX-350 boxes

Resolved In:
PR NumberSynopsisCategory: Flow Module
1832547
Minor		The flowd process crash is observed on certain SRX platforms
Product-Group=junos		On certain Junos SRX devices upon initiation of session scan, flowd process might crash due to session getting deleted/re-routed. This could result switchover of redundancy group in case of high availability.

Resolved In: junos:23.4R2-S4-J26 junos:23.4R2-S6 junos:24.2R2-S5 junos:24.4R2 junos:25.2R1 junos:25.3R1
1834338
Major		GRE traffic is getting blocked due to a software programming issue and MTU going below minimum value
Product-Group=junos		On Junos OS SRX platforms with GRE (Generic Routing Encapsulation) configured, due to a software programming issue, some threads have incomplete information while processing the data and even if "no-path-mtu-discovery" or "no-gre-path-mtu-discovery" is configured, the MTU going below minimum value (IPv4- 578, IPv6 1280) resulting in the GRE traffic being blocked i.e. complete traffic impact.

Resolved In: junos:24.2R2 junos:24.4R2 junos:25.1R1 junos:25.2R1
1873580
Major		The TCP session is not closing properly on the SRX4600 and SRX5K platforms after receiving the FIN-ACK message causing packets to drop for new session if reusing same source port
Product-Group=junos		On SRX4600 and SRX5K platforms, when IDP (Intrusion Detection and Prevention) is configured in global policy, TCP (Transmission Control Protocol) sessions are not closing immediately after receiving the final FIN-ACK (finish-acknowledgement) message. If one end has initiated TCP session close by sending FIN packet and other end has sent an acknowledgement of FIN, IDP ignores the TCP session during processing of ACK packet as policy which accepts TCP packet is not configured with IDP application service. If other end device is reusing the same source port to initiate new connections, device drops because the existing session is still active.

Resolved In: junos:24.2R2-S4 junos:24.4R2 junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: SRX Datapath Multicast Solution
1899131
Major		Multicast packets are getting dropped when multicast is configured in strict-ordering mode
Product-Group=junos		On Junos OS SRX1600 platforms, when multicast is configured in strict-ordering mode, and certain threads are dedicated to processing multicast traffic, some multicast packets get dropped. This occurs due to the way the system handles message processing in this configuration, which can impact multicast traffic forwarding.

Resolved In: junos:24.4R2-S3 junos:25.4R2 junos:26.1R1 junos:26.2R1
PR NumberSynopsisCategory: Layer 2 Control Module
1930380
Major		The hash collision for storm control profile indices will result in an l2ald process crash
Product-Group=junos		On all Junos OS platforms and Junos OS Evolved platforms which supports storm control, when a different storm-control profile is applied for interface where these profile have same profile index allocated then the storm control profile configuration and system state will not be in sync and a different profile will be applied for interface binding due to profile index collision which results into l2ald process crash.

Resolved In: evo:23.4R2-S8-EVO evo:24.4R2-S4-EVO evo:25.2R2-EVO evo:25.4R2-EVO evo:26.1R1-EVO evo:26.2R1-EVO junos:23.4R2-S8 junos:24.2R2-S5 junos:24.4R2-S4 junos:25.2R2 junos:25.4R1-S2 junos:25.4R2 junos:26.1R1 junos:26.2R1
PR NumberSynopsisCategory: Label Distribution Protocol
1852934
Major		The rpd process crash is seen during RE switchover
Product-Group=junos		On Junos and Junos OS Evolved dual RE (Routing-Engine) platforms with LDP (Label Distribution Protocol) configuration, an rpd process crash in the new master RE is observed during a RE switchover.

Resolved In: evo:25.3R1-EVO junos:25.3R1
1906611
Major		Crash in the rpd process after LDP P2MP LSP Identifier reaches its maximum value and rolls over, due to duplicate identifier allocation
Product-Group=junos		On all Junos OS and Junos OS Evolved versions that support Label Distribution Protocol Point-to-Multipoint Label Switched Paths (LDP P2MP LSPs), the rpd process (routing protocol daemon) crashes when an LSP Identifier reaches its 24-bit maximum value (224 1 = 16, 777, 215) and rolls over to the starting value because a duplicate identifier is incorrectly allocated. This condition occurs only after prolonged tunnel flapping (typically more than 16 million flaps). When the rpd process crashes, routing convergence is briefly disrupted, and services relying on label-switched traffic are impacted until the process automatically restarts.

Resolved In: evo:26.1R1-EVO junos:26.1R1
PR NumberSynopsisCategory: Multiprotocol Label Switching
1889546
Major		MPLS ping/trace not working for direct peers via routing-instance over MPLS protocols
Product-Group=junos		On all Junos and Junos OS Evolved platforms, when a routing instance is configured at the destination device, an echo request packet is received over this routing instance interface. This routing instance should have a valid route to reach the source device. But the default routing instance should not have a valid route to reach the source device. This issue is not specific to MPLS ping over SR alone. This issue is applicable for all the protocols MPLS ping.

Resolved In: evo:24.2R2-S5-EVO evo:24.4R2-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:23.4R2-S7 junos:23.4R2-S8 junos:24.2R2-S2 junos:24.2R2-S5 junos:24.4R2-S2 junos:25.2R1-S2 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: Multicast for L3VPNs
1888630
Major		MVPN Source PE might incorrectly send mcast traffic on SPT while actual receiver is still on RPTree
Product-Group=junos		In currently flow when a provider tunnel is being deleted, it is assumed the cmcast routes associated to the ptnl would've have been updated before. This is fine for inclusive tunnels, however for selective tunnels especially wild card scenarios the cmcast routes may not be updated. So in cases where the ptnl is deleted like configuration based removal or underlying tunnel going down, there is chance that the forwarding routes are still not deleted. The cmcasts are deleted later in the flow but when they are deleted the corresponding forwarding routes are still not deleted since there is no corresponding ptnl for the cmcast. This will create issues if forwarding is supposed to happen via different forwarding entry like a *, G entry but since the more specific S, G stale entry exists, traffic will hit the later and lead to unexpected behavior like traffic black-holing if S, G is Pruned entry.

Resolved In: evo:24.2R2-S3-EVO evo:24.4R2-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:24.2R2-S3 junos:24.4R2 junos:25.2R2 junos:25.3R1 junos:25.4R1
1902405
Major		The rpd process crash is observed with MVPN and RIB sharding enabled
Product-Group=junos		On Junos MX and Junos Evolved PTX platforms , with RIB sharding enabled and if either IPv4 or IPv6 address family is disabled in MVPN (multicast virtual private network), the unicast route flow from shard tries to access MVPN data structures without validation leading to rpd (Routing Protocol Daemon) process crash.

Resolved In: evo:24.4R2-S1-EVO evo:25.2R1-S2-EVO evo:25.2R2-EVO evo:25.4R1-EVO junos:24.2R2-S3 junos:24.4R2-J2 junos:24.4R2-S1 junos:25.2R1-S2 junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: Path computation client daemon
1929225
Critical		The pccd process crashes when muliple LSP updates are received from PCE
Product-Group=junos		On all Junos and Junos Evolved platforms with PCEP (Path Computation Element Protocol) configured, the pccd process crash is seen when multiple LSP (Label Switched Path) updates are received in a single PCE (Path Computation Element) message. The LSP update sent by the PCE will not get programmed into the forwarding plane and LSP states will not be updated till the pccd process restarts.

Resolved In: evo:23.4R2-S8-EVO evo:25.2R2-EVO evo:25.4R2-EVO evo:26.2R1-EVO junos:23.4R2-S8 junos:24.2R2-S5 junos:24.4R2-S4 junos:25.2R2 junos:25.4R1-S2 junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: Protocol Independant Multicast
PR NumberSynopsisCategory: Issues related to PKI daemon
1839090
Major		Traffic loss due to tunnel establishment failure in HA setup
Product-Group=junos		On Junos platforms, during PKI (Public Key Infrastructure) certificate renewal in an HA (High Availability) setup, if the PKI daemon on the secondary node is busy, mismatched certificates will occur. If a failover happens, the mismatched certificates are used for IKE (Internet Key Exchange) tunnel establishment, causing tunnel failure and resulting in traffic loss.

Resolved In: evo:23.4R2-S4-EVO evo:24.2R2-EVO evo:24.4R1-EVO evo:24.4R2-EVO junos:23.4R2-S3 junos:23.4R2-S4 junos:24.2R2 junos:24.4R1 junos:24.4R2 junos:24.4R2-S1 junos:25.1R1
1919729
Major		SRX 2300 SRX 4700 SRX4300 and SRX1600 Enter System Halt or Amnesiac State After Reboot When TPM/MEK is Enabled
Product-Group=junos		On SRX4300, SRX 4700, SRX 2300 , SRX 1600 platforms When Master password and Master Encryption Key is set on the device and rebooted , the system was getting into amnesiac state.

Resolved In: junos:24.2R2-S5 junos:24.4R2-S4 junos:26.1R1 junos:26.2R1
PR NumberSynopsisCategory: Periodic Packet Management Daemon
1931633
Major		PFE crash due to memory corruption when STP is enabled
Product-Group=junos		On all Junos Platforms, a rare memory corruption condition may occur in the Packet Forwarding Engine (PFE) when Spanning Tree Protocol (STP) is enabled and operating in default (distributed) mode. When the issue is triggered, the PFE crashes and a dc-pfe core file is generated. The exact trigger for the memory corruption is currently unknown.

Resolved In: evo:23.4R2-S8-EVO evo:24.2R2-S5-EVO evo:24.4R2-S4-EVO evo:25.2R2-S1-EVO evo:25.4R2-EVO evo:26.2R1-EVO junos:23.4R2-S8 junos:24.2R2-S5 junos:24.4R2-S4 junos:25.2R2-S1 junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: PTX10K Routing Engine
1849593
Major		After code upgrade to 22.4R3-S5.11 S/Ns of both the CBs are Same
Product-Group=junos		As part of this PR, both control boards in the router display the same serial number, which is not expected. This happened because the system was trying to read serial numbers using a specific path (0x59 address) that isn't accessible on the backup board.

Resolved In: junos:22.4R3-S5-J3 junos:22.4R3-S6 junos:22.4R3-S7 junos:22.4R3-S8 junos:24.2R2 junos:24.4R1 junos:24.4R2 junos:25.1R1 junos:25.2R1
PR NumberSynopsisCategory: QFX PFE Class of Services
1786119
Minor		QFX5k : The pps rate for egress interface becomes zero after removing one of VCP ports
Product-Group=junos		On QFX5k virtual-chassis platforms working with 5e image, the pps rate display output for the egress interface would become zero after removing one of the VCP ports. The traffic is received as expected and it is only not displayed in the output.

Resolved In: junos:22.2R3-S5 junos:23.4R2-S4 junos:24.2R2 junos:24.4R1
PR NumberSynopsisCategory: QFX analyzer, sflow
1850213
Minor		L3 multicast traffic not forwarded when multi-homing node is acting as source in VXLAN
Product-Group=junos		When Group Based Policy (GBP) is enabled on Junos OS and Junos OS Evolved, Layer 3 multicast traffic originating from a Multi-homing (MH) source node is not forwarded.

Resolved In: junos:24.2R2-S1 junos:24.4R2-S1 junos:25.2R1
PR NumberSynopsisCategory: QFX5K JUNOS Interface, MACSec, Optics, SDK, PHY
1773567
Major		100G optics settings to CAUI4 on Junos QFX5120-48T platforms
Product-Group=junos		The port interface on the 100G optics of the QFX5120-48T platform is incorrectly configured

Resolved In: junos:22.2R3-S7 junos:22.4R3-S7 junos:23.2R2-S4 junos:23.4R2-S5 junos:23.4R2-S6 junos:24.2R2 junos:24.4R1 junos:25.1R1 junos:25.2R1
PR NumberSynopsisCategory: Issues related to krt-async routing infrastructure
1866522
Major		VPLS session stays down after interface flaps
Product-Group=junos		An LSI IFL remains in RPD even after being deleted by the interface manager daemon. It is visible in show interface routing but not in show interfaces, indicating that RPD still holds the IFL despite its removal elsewhere. rpd-agent does not send a delete message to RPD due to a reference count issue. Another daemon?likely l2ald?still holds a reference to the IFL. rpd-agent only sends the delete once all references are cleared, which doesn't happen in this case. The fix is to send a "delete pending" message from rpd-agent to RPD. RPD will treat this as a delete and remove the IFL, ensuring consistency across the system.

Resolved In: evo:23.2R2-S5-EVO evo:23.2X2-EVO evo:23.4R2-S8-EVO evo:24.2R2-S4-EVO evo:24.4R2-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:26.2R1-EVO junos:23.4R2-S8 junos:25.2R2 junos:25.3R1
PR NumberSynopsisCategory: Shard routing infrastructure within RPD
1757915
Major		The rpd process crashes when processing multipath routes with mixed indirect and composite next-hops under rib-sharding
Product-Group=junos		On all Junos and Junos OS Evolved platforms, when rib-sharding is enabled and RT (Route Target) multipath routes containing both indirect and composite next-hop types are processed, the rpd (Routing Protocol Daemon) process will crash due to incorrect handling during the next-hop copy operation from RIB (Routing Information Base) shards to the main RIB thread. An rpd crash results in all routing protocols going down and causes a brief traffic disruption until the rpd process restarts.

Resolved In: evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:23.2R2-S2-J9 junos:23.4R2-S5 junos:24.4R2-S2-J8 junos:24.4R2-S3 junos:25.2R2 junos:25.2R2-S1 junos:25.3R1 junos:25.4R1 junos:25.4R2 junos:26.1DCB
PR NumberSynopsisCategory: PTX10K platform specific fabric PRs
1900242
Critical		Traffic loss seen due to SIB init failures on PTX10016 and PTX10008 platforms
Product-Group=junos		On Junos OS Evolved based PTX10K8 and PTX10K16 platforms, Switch Interface Board (SIB) init failures are observed after system reboot. Traffic loss is seen as SIBs are impacted.

Resolved In: evo:23.2R2-S4-EVO evo:23.2R2-S5-EVO evo:24.4R2-S3-EVO evo:25.3R1-EVO evo:25.4R1-EVO evo:25.4R2-EVO junos:23.2R2-S5 junos:23.4R2-S6 junos:23.4R2-S8 junos:24.2R2-S3 junos:24.4R2-S1 junos:24.4R2-S2 junos:25.2R1-S2 junos:25.2R2 junos:25.4R1 junos:JUNOS_232_R2_S4_EVO_BRANCH
PR NumberSynopsisCategory: SRX branch platforms
1934517
Major		SRX380 XE interface flap on every configuration commit with 1G SFP transceivers
Product-Group=junos		On the SRX380 platforms, in both cluster and standalone modes, the XE interfaces with 1G SFP fiber transceivers flap once after every configuration commit, causing the device to temporarily lose upstream reachability.

Resolved In: junos:23.4R2-S8 junos:24.2R2-S5 junos:25.2R2-S1 junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: MPC7E, MPC8E and MPC9E timing and synchronization
1803105
Major		PTP attribute changes on upstream device causes best clock master slot switchover
Product-Group=junos		On all MX platforms(except MX80) with multi line card chassis, when PTP slave or stateful streams are configured across multiple linecards with clock from same PTP time provider and the announce msg parameters changes from the upstream device, the best master clock (BMC) slot switchover is observed and is restored back within few seconds. Although the slot time interval is very less, it can still lead to major impact as the active PTP slot and clock path is switched over and results in re-routing of the clocks.

Resolved In: evo:24.4R1-EVO evo:25.1R1-EVO junos:23.4R2-S6 junos:24.2R2-S5 junos:24.4R1 junos:24.4R2 junos:25.1R1
PR NumberSynopsisCategory: ZT/YT pfe CDA issues
1882845
Critical		MPC 10/11/12E, LC9600 and LC4800 Line cards and MX304, interface statistics stop after interrupt
Product-Group=junos		On all MX platforms with MPC 10/11/12E, LC9600 and LC4800 Line cards and MX304, in a race condition related to the interrupt handling, interface counters are stuck and not incrementing. Issue not reproducible and there is no service impact due to this issue.

Resolved In: evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:21.2X35-J1 junos:23.4R2-S5-J34 junos:23.4R2-S5-J41 junos:23.4R2-S6 junos:24.2R1-S2-J5 junos:24.2R2-J9 junos:24.2R2-S1-J7 junos:24.2R2-S3 junos:24.4R2-S1 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: ZT/YT pfe l3 forwarding issues
1886395
Major		FPC crash is seen on Junos platforms in a rare scenario
Product-Group=junos		On all Junos platforms, FPC (Flexible PIC Concentrator) crashes due to panic caused by incorrect handling of an application. This causes service impact since the card restarts after crash.

Resolved In: evo:25.2R2-EVO evo:25.4R1-EVO junos:23.4R2-S4-J23 junos:23.4R2-S4-J30 junos:23.4R2-S6 junos:24.2R2-S2-J16 junos:24.2R2-S4 junos:25.2R2 junos:25.4R2
PR NumberSynopsisCategory: Issues related to broadband edge apps (PPP, DHCP) on Trio ch
1924812
Minor		Dual stack PPPoE/DHCPv6 syslog reports PFE_ERROR_INVALID_STATE fd01:3333:b205:44f1:: /64 => source lookup is not enabled for flow 18558885
Product-Group=junos		Dual stack PPPoE/DHCPv6 syslog reports PFE_ERROR_INVALID_STATE fd01:3333:b205:44f1:: /64 => source lookup is not enabled for flow 18558885

Resolved In: evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: Issues related to NETCONF
1858635
Critical		ACX Series vmcore crash when netconf notifications are enabled
Product-Group=junos		On ACX7024, ACX710032C, and ACX7348 platforms running Junos OS Evolved, enabling netconf notifications with the command "set system services netconf notification" may cause a memory leak. This results in a control plane crash (vmcore). Forwarding plane remains unaffected.

Resolved In: evo:23.4R2-S8-EVO evo:24.2R2-S4-EVO evo:24.2X2-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO evo:26.1R1-EVO evo:26.2R1-EVO junos:23.4R2-S8 junos:24.2R2-S4 junos:24.4R2 junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: MX10K linecard
1898825
Major		Unexpected line card restart due to timing condition
Product-Group=junos		On Junos platforms using line cards LC480 and LC2101, a timing defect in the embedded microkernel thread handling logic causes a panic when a thread attempts to yield execution while interrupt processing is still active. This panic results in a line card reboot.

Resolved In: evo:24.4R2-S3-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:23.4R2-S8 junos:24.2R2-S2-J9 junos:24.2R2-S3-J7 junos:24.2R2-S4 junos:24.4R2-S3 junos:24.4R2-S4 junos:25.2R2 junos:25.2R2-S1 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: VMHOST platforms software
1927342
Minor		Junos VMhost platforms restart unexpectedly due to deadlock
Product-Group=junos		On all Junos VMhost platforms, when Junos performs disk access, a rare deadlock involving FreeBSD kernel processes will occur. This condition causes FreeBSD kernel panic, resulting in crash of vmcore and an unexpected device restart, leading to temporary system unavailability.

Resolved In: junos:22.4R3-S10 junos:22.4R3-S9 junos:22.4X50 junos:23.2R2-S7 junos:23.2R2-S8 junos:23.4R2-S8 junos:23.4X12 junos:23.4X13 junos:24.2R2-S5 junos:25.2R2-S1 junos:25.2R2-S2 junos:26.2R1
PR NumberSynopsisCategory: Virtual Private LAN Services
1885690
Major		rpd crash on backup RE during switchover due to VPLS Auto-Site mismatch
Product-Group=junos		An rpd core triggered on the backup Routing Engine after a switchover due to an assertion failure in within the context of L2VPN VPLS auto-site processing, caused by a mismatch between the auto-site claim-id/site-id and the local site-id associated with interfaces in the VPLS IFL repository for a given instance, leading to stale interface entries being referenced during auto-site processing.

Resolved In: evo:24.4R2-S4-EVO evo:25.4R2-EVO evo:26.1R1-EVO evo:26.2R1-EVO junos:25.4R2 junos:26.1R1 junos:26.2R1

 

Modification History

First publication 2026-05-27

Update for recall 2026-10-14