dbcve.org
JunosOperating system · Juniper

CVE-2025-59959

MEDIUM · 5.5 CVSS v3.1 Published 2026-01-15
Fix available
A fix is available. Upgrade to 22.4 or later.
See remediation →
57/100
Remediation priority · Elevated
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 Untrusted Pointer Dereference vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows a local, authenticated attacker with low privileges to cause a Denial-of-Service (DoS). When the command 'show route < ( receive-protocol | advertising-protocol ) bgp > detail' is executed, and at least one of the routes in the intended output has specific attributes, this will cause an rpd crash and restart. 'show route ... extensive' is not affected. This issue affects: Junos OS:  * all versions before 22.4R3-S8, * 23.2 versions before 23.2R2-S5, * 23.4 versions before 23.4R2-S5, * 24.2 versions before 24.2R2-S2, * 24.4 versions before 24.4R2; Junos OS Evolved: * all versions before 22.4R3-S8-EVO,  * 23.2 versions before 23.2R2-S5-EVO, * 23.4 versions before 23.4R2-S6-EVO, * 24.2 versions before 24.2R2-S2-EVO, * 24.4 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

An untrusted pointer dereference vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS allows a local, authenticated attacker with low privileges to crash rpd by executing 'show route <receive-protocol|advertising-protocol> bgp detail' when specific route attributes are present in the output.

MitigationApply the vendor-supplied patches: upgrade to 22.4R3-S8, 23.2R2-S5, 23.4R2-S5, 24.2R2-S2, or 24.4R2 or later for Junos OS (or corresponding -EVO versions for Junos OS Evolved).

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.4= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 Junos product type
    Run 'show version' and look for 'Junos OS' or 'Junos OS Evolved' in the output
    Affected if Product is Junos OS or Junos OS Evolved (both are affected)
  2. Check installed Junos version
    Run 'show version' and note the exact version number (e.g., 22.4R1, 23.2R1, etc.)
    Affected if Version matches or falls within: < 22.4; = 22.4; = 23.2; = 23.4; = 24.2; = 24.4
  3. Verify BGP is configured
    Run 'show configuration protocols bgp' to see if BGP protocol is configured
    Affected if BGP is configured and running - the vulnerable command targets BGP routes
  4. Check for route entries that could trigger the flaw
    Run 'show route receive-protocol bgp detail' or 'show route advertising-protocol bgp detail' and examine output for route attributes
    Affected if Command output displays BGP routes with specific route attributes present (the exact attributes that trigger the flaw are internal to the vulnerability)
  5. Confirm rpd process status
    Run 'show system processes rpd' to verify the routing daemon is running
    Affected if rpd is active - this is the process vulnerable to the crash

You are affected if your Junos OS or Junos OS Evolved version is 22.4, 23.2, 23.4, 24.2, or 24.4 (or any version below 22.4), BGP is configured, and the vulnerable rpd daemon is running.

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.4 or later
Fixed in 22.4
Interim mitigation

Apply the vendor-supplied patches: upgrade to 22.4R3-S8, 23.2R2-S5, 23.4R2-S5, 24.2R2-S2, or 24.4R2 or later for Junos OS (or corresponding -EVO versions for Junos OS Evolved).

Recommended fix High confidence

22.4R3-S8, 23.2R2-S5, 23.4R2-S5 (or 23.4R2-S6-EVO for Evolved), 24.2R2-S2, or 24.4R2 - depending on starting branch

  1. 1. Identify the current Junos OS or Junos OS Evolved version installed by running 'show version'
  2. 2. Determine which version branch you are currently running (22.4, 23.2, 23.4, 24.2, or 24.4)
  3. 3. For branch 22.4: upgrade to 22.4R3-S8 or later
  4. 4. For branch 23.2: upgrade to 23.2R2-S5 or later
  5. 5. For branch 23.4: upgrade to 23.4R2-S5 (OS) or 23.4R2-S6-EVO (Evolved) or later
  6. 6. For branch 24.2: upgrade to 24.2R2-S2 or later
  7. 7. For branch 24.4: upgrade to 24.4R2 or later
  8. 8. Verify the upgrade was successful and rpd is running by executing 'show route receive-protocol bgp <peer> detail' to confirm functionality
Caveat Standard Junos upgrade considerations apply - verify hardware compatibility, review release notes for behavioral changes, and plan maintenance window as rpd will restart during upgrade

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

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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