Skip to content
VulniPulse
Medium5.8Juniper Networks

Medium [CVE-2026-33773] 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

This medium-severity Juniper Networks advisory covers CVE-2026-33773 affecting Junos OS, Junos, QFX.

CVE-2026-33773 Published Apr 9, 2026Updated by vendor Jun 17, 2026
Affected products & platforms
Juniper NetworksSwitchesJunosEX / QFX SwitchesEX4100
Open vendor advisory

Android app · Google Play

Monitor future Juniper Networks CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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.

Affected products named by the advisory: EX.

Affected products named by the advisory: EX.

Affected versions
  • 23.4
  • 24.2

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.