dbcve.org
JunosOperating system · Juniper

CVE-2025-52989

MEDIUM · 5.1 CVSS v3.1 Published 2025-07-11
Fix available
A fix is available. Upgrade to 22.2 / 22.4 or later.
See remediation →
53/100
Remediation priority · Moderate
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
An Improper Neutralization of Delimiters vulnerability in the UI of Juniper Networks Junos OS and Junos OS Evolved allows a local, authenticated attacker with high privileges to modify the system configuration. A user with limited configuration and commit permissions, using a specifically crafted annotate configuration command, can change any part of the device configuration. This issue affects:  Junos OS:  * all versions before 22.2R3-S7, * 22.4 versions before 22.4R3-S7, * 23.2 versions before 23.2R2-S4, * 23.4 versions before 23.4R2-S4, * 24.2 versions before 24.2R2-S1, * 24.4 versions before 24.4R1-S2, 24.4R2; Junos OS Evolved: * all versions before 22.4R3-S7-EVO, * 23.2-EVO versions before 23.2R2-S4-EVO, * 23.4-EVO versions before 23.4R2-S5-EVO,  * 24.2-EVO versions before 24.2R2-S1-EVO * 24.4-EVO versions before 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

This is a privilege escalation vulnerability in Juniper Networks Junos OS and Junos OS Evolved where an authenticated attacker with high privileges but limited configuration permissions can use a specifically crafted 'annotate' configuration command to modify any part of the system configuration, effectively bypassing permission boundaries.

MitigationApply the vendor-supplied patches for Junos OS and Junos OS Evolved as listed in the advisory, upgrading to the specified minimum versions for each 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
JunosOperating system
Affected:< 22.2= 22.2= 22.4= 23.2= 23.4= 24.2= 24.4
Junos Os EvolvedOperating system
Affected:< 22.4= 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
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
Low

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

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 installed Junos OS version
    Run 'show version' or 'request system version' on the device CLI to obtain the exact Junos OS version number
    Affected if The displayed version matches any of the affected versions: < 22.2, = 22.2, = 22.4, = 23.2, = 23.4, = 24.2, = 24.4 (for Junos OS) or < 22.4, = 22.4, = 23.2, = 23.4, = 24.2, = 24.4 (for Junos OS Evolved)
  2. Confirm device is running Junos OS or Junos OS Evolved
    Run 'show version' and identify whether the output indicates 'Junos OS' or 'Junos OS Evolved'
    Affected if The device runs either Junos OS or Junos OS Evolved and the version falls within the affected ranges listed above
  3. Identify users with elevated privileges but limited configuration permissions
    Review user accounts and their permission sets using 'show configuration system login' and 'show configuration access' to identify users who have high privileges (such as 'super-user' or 'operator') but are intentionally restricted from full configuration access
    Affected if Such restricted-but-elevated user accounts exist on the device, creating the prerequisite user profile for this privilege escalation
  4. Audit recent configuration changes involving the annotate command
    Review configuration change logs, commit history, or system logs for any 'annotate' configuration commands that may have been issued, especially by users with limited permissions. Use 'show system commit' and filter for annotate-related operations if available
    Affected if There are commit log entries showing 'annotate' commands were executed, particularly by users who should not have had permission to modify restricted configuration areas

A device is affected if it runs a vulnerable Junos OS or Junos OS Evolved version within the listed ranges AND has users with elevated but limited configuration permissions, as the vulnerability allows such users to bypass permission boundaries via the annotate command.

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 / 22.4 or later
Fixed in 22.222.4
Interim mitigation

Apply the vendor-supplied patches for Junos OS and Junos OS Evolved as listed in the advisory, upgrading to the specified minimum versions for each branch.

Recommended fix High confidence

Junos OS: 22.2R3-S7+, 22.4R3-S7+, 23.2R2-S4+, 23.4R2-S4+, 24.2R2-S1+, 24.4R1-S2+ or 24.4R2+; Junos OS Evolved: 22.4R3-S7-EVO+, 23.2R2-S4-EVO+, 23.4R2-S5-EVO+, 24.2R2-S1-EVO+, 24.4R2-EVO+

  1. 1. Identify the current Junos OS or Junos OS Evolved version installed on the device using 'show version'
  2. 2. Based on the current version branch, plan upgrade to the fixed point release: For 22.2 branch upgrade to 22.2R3-S7 or later; For 22.4 branch upgrade to 22.4R3-S7 or later; For 23.2 branch upgrade to 23.2R2-S4 or later; For 23.4 branch upgrade to 23.4R2-S4 or later; For 24.2 branch upgrade to 24.2R2-S1 or later; For 24.4 branch upgrade to 24.4R1-S2 or later, or 24.4R2
  3. 3. Download the appropriate upgrade package from the Juniper support portal (supportportal.juniper.net)
  4. 4. Back up the current device configuration using 'request system configuration backup'
  5. 5. Transfer the upgrade package to the device using SCP or FTP
  6. 6. Initiate the software upgrade using 'request system software add <package-name>' and reboot the device
  7. 7. After reboot, verify the new version is installed using 'show version' and confirm the fix is applied
  8. 8. Verify the configuration integrity using 'commit check'
Caveat Standard Junos upgrade precautions apply - review release notes for any compatibility concerns and ensure configuration compatibility before upgrading

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

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52989 — 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-52989 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