dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2025-52954

HIGH · 7.8 CVSS v3.1 Published 2025-07-11
Fix available
A fix is available. Upgrade to 22.2 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A Missing Authorization vulnerability in the internal virtual routing and forwarding (VRF) of Juniper Networks Junos OS Evolved allows a local, low-privileged user to gain root privileges, leading to a system compromise. Any low-privileged user with the capability to send packets over the internal VRF can execute arbitrary Junos commands and modify the configuration, and thus compromise the system.  This issue affects Junos OS Evolved:  * All versions before 22.2R3-S7-EVO,  * from 22.4 before 22.4R3-S7-EVO,  * from 23.2 before 23.2R2-S4-EVO,  * from 23.4 before 23.4R2-S5-EVO,  * from 24.2 before 24.2R2-S1-EVO * from 24.4 before 24.4R1-S2-EVO, 24.4R2-EVO.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Missing authorization in internal VRF allows any low-privileged local user with packet-sending capability on the internal VRF to execute arbitrary Junos OS commands with root privileges and modify system configuration, enabling complete system compromise.

MitigationApply the vendor-supplied patches: upgrade to 22.2R3-S7-EVO, 22.4R3-S7-EVO, 23.2R2-S4-EVO, 23.4R2-S5-EVO, 24.2R2-S1-EVO, or 24.4R1-S2-EVO/24.4R2-EVO as appropriate for each affected branch.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Junos Os EvolvedOperating system
Affected:< 22.2= 22.2= 22.4= 23.2= 23.4= 24.2= 24.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Junos OS Evolved version
    Execute `show version` or `show version detail` on the device CLI to retrieve the exact software version
    Affected if The displayed version matches any of the following: below 22.2, 22.2, 22.4, 23.2, 23.4, 24.2, or 24.4 (including variants like 22.2R1, 22.4R1, etc.)
  2. Confirm the device is running Junos OS Evolved
    Verify the output from `show version` indicates "Junos OS Evolved" rather than classic Junos OS
    Affected if The platform is Junos OS Evolved and the version falls in the affected list from step 1
  3. Check for internal VRF configuration
    Review the VRF configuration using `show configuration | match vrf` or `show configuration routing-instances` to identify if internal VRFs are defined
    Affected if Internal VRF instances are configured on the device
  4. Identify users with packet-sending capability on internal VRF
    Examine user permissions and VRF access controls via `show configuration system login` and review any packet-sending or VRF-access permissions assigned to non-privileged accounts
    Affected if Any low-privileged local user account has been granted packet-sending capability or access to the internal VRF

The device is affected if it runs Junos OS Evolved with a version in the affected list and has internal VRF configured with any low-privileged user having packet-sending capability on that VRF.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 22.2 or later
Fixed in 22.2
Interim mitigation

Apply the vendor-supplied patches: upgrade to 22.2R3-S7-EVO, 22.4R3-S7-EVO, 23.2R2-S4-EVO, 23.4R2-S5-EVO, 24.2R2-S1-EVO, or 24.4R1-S2-EVO/24.4R2-EVO as appropriate for each affected branch.

Recommended fix High confidence

For 22.2 branch: upgrade to 22.2R3-S7-EVO; for 22.4 branch: upgrade to 22.4R3-S7-EVO; for 23.2 branch: upgrade to 23.2R2-S4-EVO; for 23.4 branch: upgrade to 23.4R2-S5-EVO; for 24.2 branch: upgrade to 24.2R2-S1-EVO; for 24.4 branch: upgrade to 24.4R2-EVO or 24.4R1-S2-EVO

  1. 1. Identify the currently running Junos OS Evolved version using 'show version' command
  2. 2. Based on the current version, determine the appropriate upgrade path to a fixed release
  3. 3. Download the appropriate fixed Junos OS Evolved image from the Juniper Networks support portal
  4. 4. Before upgrading, backup the current configuration using 'request system backup' or similar
  5. 5. Transfer the upgrade image to the device and initiate the upgrade with 'request system software add <image> reboot'
  6. 6. After the device reboots, verify the new version is running with 'show version'
  7. 7. Verify the fix is applied by confirming the system is running a patched version as specified in the fixed releases
Caveat Review Juniper Networks release notes for any compatibility concerns or configuration changes between your current version and the target fixed release before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Os Evolved Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52954 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-52954 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data