Affects Juniper Junos management on widely deployed network infrastructure; unauthenticated root takeover can disrupt enterprise and provider networks.
CVE-2026-101954
Unauthenticated root takeover via Juniper J‑Web/NETCONF management.
Is CVE-2026-101954 being exploited?
Not confirmed. CVE-2026-101954 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.49% probability of exploitation in the next 30 days.
How severe is CVE-2026-101954?
CVE-2026-101954 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-101954?
Yes. A fix has been recorded for CVE-2026-101954. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-101954 affect?
CVE-2026-101954 affects Juniper Junos OS, Juniper Junos OS Evolved, J‑Web (HTTP/HTTPS) management, NETCONF session handling. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-101954?
Install Juniper's patches immediately; disable J‑Web if unused and restrict management access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote unauthenticated attacker can bypass auth via J‑Web/NETCONF to obtain root config access and fully compromise devices.
Immediate action required
- affected>= 25.2 and < 25.2R2-S2
- affected>= 25.4 and < 25.4R1-S3
- affected>= 26.2 and < 26.2R1-S2
- affected>= 25.2 and < 25.2R2-S2-EVO
- affected>= 25.4 and < 25.4R1-S3-EVO
- affected>= 26.2 and < 26.2R1-S2-EVO
- affected23.4X100
- affected>= 25.2X100 and < 25.2X100-D35-EVO
- affected>= 25.4X300 and < 25.4X300-D40-EVO
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.