highCVE-2026-33801

CVE-2026-33801 in Junos OS

An Improper Check for Unusual or Exceptional Conditions vulnerability in the routing protocol daemon (RPD) of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent, unauthenticated attacker sending a specific BGP update over an established BGP session to cause a...

ProductJunos OS
CVSS7.1
EPSSNot scored yet
UpdatedJuly 15, 2026

Quick answer

Juniper Networks Junos OS should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • Junos OS 25.2 to before 25.2R2
  • Junos OS Evolved 25.2 to before 25.2R2-EVO

Fixed versions

  • Junos OS 25.2R2 or later
  • Junos OS Evolved 25.2R2-EVO or later

How to fix it

Update Junos OS. The old network OS can allow denial of service, data exposure, or bypass, depending on the CVE.

  1. Check the exact Juniper platform and release train.
  2. Upgrade to a fixed release: Junos OS 25.2R2 or later, Junos OS Evolved 25.2R2-EVO or later.
  3. Follow Juniper maintenance and rollback guidance.
  4. Watch routing, VPN, flow, CPU, and crash logs after the update.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Run show version and confirm the fixed Junos release is installed.
  • Scan again and confirm CVE-2026-33801 is gone.

Related categories

Trusted references

FAQ

What is affected by CVE-2026-33801?

Juniper Networks Junos OS versions listed as affected should be reviewed: Junos OS 25.2 to before 25.2R2, Junos OS Evolved 25.2 to before 25.2R2-EVO.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.