# CVE-2026-33773: Security feature bypass in Junos OS

> An attacker can bypass egress filters on specific Juniper switches if identical filters are applied to both IRB and physical interfaces, allowing blocked traffic to pass.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2026
- **Updated:** 13 Apr 2026
- **Also known as:** GHSA-m7p5-cqg5-94p6

## What is CVE-2026-33773?

CVE-2026-33773 is a medium-severity vulnerability in Juniper Junos, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-1419 (Incorrect Initialization of Resource)

## Which versions are affected by CVE-2026-33773?

It affects 1 product.


Products: Juniper Junos.

## How do I fix CVE-2026-33773?

No fix has been published for CVE-2026-33773 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33773 being exploited?

There is no known exploitation of CVE-2026-33773 in the wild and no public exploit code.

## Other vulnerabilities in Juniper Junos

- [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild)
- [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild)
- [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild)
- [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild)
- [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33773 and fix it if it is affected.

What it is: CVE-2026-33773 is a medium-severity vulnerability in Juniper Junos, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33773 in the wild and no public exploit code.

Affected product: Juniper Junos. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33773/ (Markdown: https://insights.sbomify.com/CVE-2026-33773/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33773
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33773
- OSV: https://osv.dev/vulnerability/CVE-2026-33773

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33773/
Summaries are generated and may contain mistakes; the official description above is the record.