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) in Juniper Networks Junos OS affects MX Series devices with certain line cards and specific Junos OS versions before 23.2R2-S6, 23.4R2-S7, 24.2R2, and 24.4R2. It arises from improper checking of firewall filters applied on non-zero loopback interfaces (lo0.n) when these interfaces are in the global VRF (default routing instance). As a result, firewall filters configured on these interfaces do not get executed, allowing an unauthenticated network attacker to bypass the firewall filter and potentially access the control-plane of the device. The issue can be observed by the absence of firewall counter matches for the filter. The vulnerability is classified under CWE-754 (Improper Check for Unusual or Exceptional Conditions). No vendor advisory or patch information is currently provided.
Potential Impact
An unauthenticated, network-based attacker can bypass configured firewall filters on affected Junos OS MX Series devices, potentially gaining unauthorized access to the device control-plane. This could lead to information disclosure or unauthorized control-plane interactions. The impact is limited to devices with specific line cards and configurations involving non-zero loopback interfaces in the default routing instance. The CVSS v3.1 base score is 6.5, indicating a medium severity with low complexity, no privileges required, and no user interaction needed.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, review configurations to avoid applying firewall filters on non-zero loopback interfaces (lo0.n) in the global VRF/default routing instance on affected MX Series devices. Monitor Juniper Networks advisories for updates and apply patches promptly once released.
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) in Juniper Networks Junos OS affects MX Series devices with certain line cards and specific Junos OS versions before 23.2R2-S6, 23.4R2-S7, 24.2R2, and 24.4R2. It arises from improper checking of firewall filters applied on non-zero loopback interfaces (lo0.n) when these interfaces are in the global VRF (default routing instance). As a result, firewall filters configured on these interfaces do not get executed, allowing an unauthenticated network attacker to bypass the firewall filter and potentially access the control-plane of the device. The issue can be observed by the absence of firewall counter matches for the filter. The vulnerability is classified under CWE-754 (Improper Check for Unusual or Exceptional Conditions). No vendor advisory or patch information is currently provided.
Potential Impact
An unauthenticated, network-based attacker can bypass configured firewall filters on affected Junos OS MX Series devices, potentially gaining unauthorized access to the device control-plane. This could lead to information disclosure or unauthorized control-plane interactions. The impact is limited to devices with specific line cards and configurations involving non-zero loopback interfaces in the default routing instance. The CVSS v3.1 base score is 6.5, indicating a medium severity with low complexity, no privileges required, and no user interaction needed.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, review configurations to avoid applying firewall filters on non-zero loopback interfaces (lo0.n) in the global VRF/default routing instance on affected MX Series devices. Monitor Juniper Networks advisories for updates and apply patches promptly once released.
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/9/2026, 10:22:26 PM
Last updated: 4/10/2026, 8:13:53 AM
Views: 5
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.