CVE-2026-33774: CWE-754 Improper Check for Unusual or Exceptional Conditions in Juniper Networks Junos OS
An Improper Check for Unusual or Exceptional Conditions vulnerability in the packet forwarding engine (pfe) of Juniper Networks Junos OS on MX Series allows an unauthenticated, network-based attacker to bypass the configured firewall filter and access the control-plane of the device. On MX platforms with MPC10, MPC11, LC4800 or LC9600 line cards, and MX304, firewall filters applied on a loopback interface lo0.n (where n is a non-0 number) don't get executed when lo0.n is in the global VRF / default routing-instance. An affected configuration would be: user@host# show configuration interfaces lo0 | display set set interfaces lo0 unit 1 family inet filter input <filter-name> where a firewall filter is applied to a non-0 loopback interface, but that loopback interface is not referred to in any routing-instance (RI) configuration, which implies that it's used in the default RI. The issue can be observed with the CLI command: user@device> show firewall counter filter <filter_name> not showing any matches. This issue affects Junos OS on MX Series: * all versions before 23.2R2-S6, * 23.4 versions before 23.4R2-S7, * 24.2 versions before 24.2R2, * 24.4 versions before 24.4R2.
AI Analysis
Technical Summary
This vulnerability (CVE-2026-33774) involves an improper check for unusual or exceptional conditions (CWE-754) in the packet forwarding engine of Juniper Networks Junos OS on MX Series devices. Specifically, firewall filters applied to non-zero loopback interfaces (lo0.n) in the global VRF/default routing instance do not get executed, allowing bypass of firewall filtering. Affected devices include MX platforms with MPC10, MPC11, LC4800, or LC9600 line cards and Junos OS versions before 23.2R2-S6, 23.4 versions before 23.4R2-S7, 24.2 versions before 24.2R2, and 24.4 versions before 24.4R2. The vulnerability enables an unauthenticated network attacker to access the control plane by circumventing firewall filters. The issue can be verified by observing that firewall counters for the filter show no matches despite traffic. No vendor advisory or patch links are provided in the data, and the remediation level is unspecified.
Potential Impact
An unauthenticated attacker on the network can bypass firewall filters applied to certain loopback interfaces on affected Junos OS MX Series devices, potentially gaining unauthorized access to the device's control plane. This could lead to information disclosure or limited control-plane impact. The CVSS score of 6.5 reflects a medium severity with low attack complexity, no privileges required, and no user interaction needed. There is no indication of known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The affected Junos OS versions are identified, and fixed versions appear to be 23.2R2-S6 or later, 23.4R2-S7 or later, 24.2R2 or later, and 24.4R2 or later. Until an official patch or update is applied, administrators should avoid applying firewall filters on non-zero loopback interfaces in the default routing instance or consider alternative configurations to mitigate bypass risk. Monitor Juniper Networks advisories for official fixes and guidance.
CVE-2026-33774: CWE-754 Improper Check for Unusual or Exceptional Conditions in Juniper Networks Junos OS
Description
An Improper Check for Unusual or Exceptional Conditions vulnerability in the packet forwarding engine (pfe) of Juniper Networks Junos OS on MX Series allows an unauthenticated, network-based attacker to bypass the configured firewall filter and access the control-plane of the device. On MX platforms with MPC10, MPC11, LC4800 or LC9600 line cards, and MX304, firewall filters applied on a loopback interface lo0.n (where n is a non-0 number) don't get executed when lo0.n is in the global VRF / default routing-instance. An affected configuration would be: user@host# show configuration interfaces lo0 | display set set interfaces lo0 unit 1 family inet filter input <filter-name> where a firewall filter is applied to a non-0 loopback interface, but that loopback interface is not referred to in any routing-instance (RI) configuration, which implies that it's used in the default RI. The issue can be observed with the CLI command: user@device> show firewall counter filter <filter_name> not showing any matches. This issue affects Junos OS on MX Series: * all versions before 23.2R2-S6, * 23.4 versions before 23.4R2-S7, * 24.2 versions before 24.2R2, * 24.4 versions before 24.4R2.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CVE-2026-33774) involves an improper check for unusual or exceptional conditions (CWE-754) in the packet forwarding engine of Juniper Networks Junos OS on MX Series devices. Specifically, firewall filters applied to non-zero loopback interfaces (lo0.n) in the global VRF/default routing instance do not get executed, allowing bypass of firewall filtering. Affected devices include MX platforms with MPC10, MPC11, LC4800, or LC9600 line cards and Junos OS versions before 23.2R2-S6, 23.4 versions before 23.4R2-S7, 24.2 versions before 24.2R2, and 24.4 versions before 24.4R2. The vulnerability enables an unauthenticated network attacker to access the control plane by circumventing firewall filters. The issue can be verified by observing that firewall counters for the filter show no matches despite traffic. No vendor advisory or patch links are provided in the data, and the remediation level is unspecified.
Potential Impact
An unauthenticated attacker on the network can bypass firewall filters applied to certain loopback interfaces on affected Junos OS MX Series devices, potentially gaining unauthorized access to the device's control plane. This could lead to information disclosure or limited control-plane impact. The CVSS score of 6.5 reflects a medium severity with low attack complexity, no privileges required, and no user interaction needed. There is no indication of known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The affected Junos OS versions are identified, and fixed versions appear to be 23.2R2-S6 or later, 23.4R2-S7 or later, 24.2R2 or later, and 24.4R2 or later. Until an official patch or update is applied, administrators should avoid applying firewall filters on non-zero loopback interfaces in the default routing instance or consider alternative configurations to mitigate bypass risk. Monitor Juniper Networks advisories for official fixes and guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- juniper
- Date Reserved
- 2026-03-23T19:46:13.668Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d822bd1cc7ad14da2ac965
Added to database: 4/9/2026, 10:05:49 PM
Last enriched: 4/17/2026, 12:24:05 PM
Last updated: 5/25/2026, 12:21:41 PM
Views: 45
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.