Vulnerability Assessment
| Weakness |
CWE
|
| Impact | This vulnerability presents a real but constrained security risk. The CVSS v4.0 score of 6.9 reflects an unauthenticated, network-based attack vector with low complexity and no privilege requirement, but the impact is limited to integrity (SI:L-scope integrity low), with no confidentiality or availability loss (VC:N, VA:N, SA:N). The EPSS probability metric (6.9) suggests moderate likelihood of exploitation, but the practical impact depends on network topology: an attacker must be able to send traffic destined for an interface where the filter should block; only then can they exploit the partial filter bypass. The vulnerability is not confirmed in the CISA Known Exploited Vulnerabilities (KEV) catalog, and no public proof-of-concept has been identified at the time of analysis. Under SSVC decision logic, this is a 'Manage' case-real security impact (traffic bypass violates defense-in-depth), but exploitation requires network proximity and specific device/version combination, and automatable exploitation is not trivially achievable without detailed knowledge of the filter configuration. Organizations running unaffected versions or without dual IRB/physical interface filter policies are not at risk. |
| Exploit ScenarioDerived | An attacker on the same network as a vulnerable EX4400 switch (or other affected SKU) observes that a filter is configured to block outbound traffic of a certain class on both an IRB interface and an attached physical interface. Due to the initialization flaw, only one of the two filters is enforced in the packet forwarding engine. The attacker sends carefully crafted traffic toward the physical interface that should be dropped by the egress filter but is instead forwarded because the filter was not properly initialized, allowing unauthorized traffic to exit the network and potentially reaching downstream systems. No public proof-of-concept has been identified, but exploitation requires network-layer access and knowledge of the filter configuration. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 09, 2026
Packet forwarding engine (pfe) in Juniper Networks Junos OS on EX4100, EX4400, EX4650, and QFX5120 devices fails to correctly initialize egress filters on IRB and physical interfaces, allowing unauthenticated network-based attackers to bypass security policies and cause integrity impact by forwarding traffic that should be blocked. The vulnerability affects Junos OS versions 23.4R2-S6 and 24.2R2-S3. EPSS score of 6.9 reflects moderate exploitation probability; no active exploitation confirmed (non-KEV status).
RemediationAI
Juniper has released patches for both affected branches: upgrade to Junos OS version 23.4R2-S7 or later for the 23.4 line, or upgrade to version 24.2R2-S4 or later for the 24.2 line. The fundamental fix corrects the packet forwarding engine's filter initialization routine to properly apply egress filters on both IRB and physical interfaces simultaneously. Until patching is possible, operators can mitigate by: (1) applying the same egress filter only on the physical interface (not on the IRB), or (2) ensuring that firewall policy enforcement is redundant at upstream network boundaries or at Layer 3 policy enforcement points. Consult Juniper advisory JSA107815 for the exact patch versions, detailed upgrade procedures, and confirmation that your device hardware SKU is addressed by the released patches.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability exists in the packet forwarding engine's (pfe) filter application logic on specific EX Series (campus Ethernet switches) and QFX Series (core routing platforms) devices. When identical inet or inet6 family filters are configured as egress policies on both an Integrated Routing and Bridging (IRB) interface and a physical interface on the same device, the filter initialization routine fails to apply both filters correctly-only one is enforced. This is classified as CWE-1419 (Incorrect Initialization with Hard-Coded Network Resource Configuration Values), indicating a fundamental resource initialization flaw in the forwarding pipeline. The affected CPE is cpe:2.3:a:juniper_networks:junos_os:*:*:*:*:*:*:*:*, though only specific hardware SKUs (EX4100, EX4400, EX4650, QFX5120) and OS versions exhibit the defect.
Know when Junos Os gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/AU:Y/R:U/RE:M
Primary rating from Vendor (juniper) · only source for this CVE.
CVSS VectorVendor: juniper
Lifecycle Timeline
2DescriptionCVE.org
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.
When the same family inet or inet6 filter is applied on an IRB interface and on a physical interface as egress filter on EX4100, EX4400, EX4650 and QFX5120 devices, only one of the two filters will be applied, which can lead to traffic being sent out one of these interfaces which should have been blocked.
This issue affects Junos OS on EX Series and QFX Series:
- 23.4 version 23.4R2-S6,
- 24.2 version 24.2R2-S3.
No other Junos OS versions are affected.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
OS command injection in the phcd phone-home daemon of Juniper Networks Junos OS and Junos OS Evolved lets an adjacent, u
Unauthenticated remote code execution with root privileges affects Juniper Networks Junos OS devices that expose the J-W
Heap-based buffer overflow in the sdxd service-deployment daemon of Juniper Networks Junos OS and Junos OS Evolved allow
A stack-based buffer overflow in the srxpfe packet forwarding process of Juniper Networks Junos OS on SRX Series devices
Unauthenticated remote code execution with elevated privileges is possible in Juniper Junos OS and Junos OS Evolved thro
Remote root code execution in the routing protocol daemon (rpd) of Juniper Junos OS is reachable through protocol-valid
Remote code execution (on Junos OS) and rpd denial of service (on Junos OS and Junos OS Evolved) result from a stack-bas
Remote code execution with root privileges on Juniper Networks Junos OS and Junos OS Evolved is possible when the routin
Remote code execution and denial of service in Juniper Networks Junos OS and Junos OS Evolved arise from a stack-based b
Unauthenticated remote attackers can gain root-level configuration access and fully compromise Juniper Junos OS and Juno
Integer underflow in the Junos OS kernel can crash a device when the Extended Echo feature (RFC 8335 ICMP probing) is co
Heap-based buffer overflow in Juniper Networks Junos OS on SRX Series devices that have Secure Vector Routing (SVR) enab
EUVD-2026-21085
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB