CVE-2026-33773
Incorrect Initialization in Juniper Junos PFE Causes Traffic Integrity Impact
Publication date: 2026-04-09
Last updated on: 2026-04-17
Assigner: Juniper Networks, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| juniper | junos | 23.4 |
| juniper | junos | 24.2 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an Incorrect Initialization of Resource issue in the packet forwarding engine (pfe) of Juniper Networks Junos OS on certain EX Series and QFX Series devices.
Specifically, when the same family inet or inet6 filter is applied both on an IRB interface and on a physical interface as an egress filter on EX4100, EX4400, EX4650, and QFX5120 devices, only one of the two filters will be applied.
This can cause traffic to be sent out through one of these interfaces that should have been blocked, allowing an unauthenticated, network-based attacker to cause an integrity impact to downstream networks.
How can this vulnerability impact me? :
The vulnerability can impact you by allowing unauthorized network traffic to pass through interfaces where it should have been blocked.
This leads to an integrity impact on downstream networks, meaning that the expected filtering and control of network traffic is compromised.
An unauthenticated attacker could exploit this to send malicious or unauthorized traffic, potentially disrupting network operations or bypassing security controls.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows an unauthenticated, network-based attacker to cause an integrity impact to downstream networks by bypassing intended traffic filtering on certain Juniper Networks devices. Such integrity impacts could potentially lead to unauthorized data flows or exposure.
However, the provided information does not explicitly describe how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.