dbcve.org
JunosOperating system · Juniper

CVE-2025-60011

MEDIUM · 5.8 CVSS v3.1 Published 2026-01-15
Fix available
A fix is available. Upgrade to 22.4 or later.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Check for Unusual or Exceptional Conditions vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause an availability impact for downstream devices. When an affected device receives a specific optional, transitive BGP attribute over an existing BGP session, it will be erroneously modified before propagation to peers. When the attribute is detected as malformed by the peers, these peers will most likely terminate the BGP sessions with the affected devices and thereby cause an availability impact due to the resulting routing churn. This issue affects: Junos OS: * all versions before 22.4R3-S8, * 23.2 versions before 23.2R2-S5 * 23.4 versions before 23.4R2-S6, * 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

A vulnerability in Juniper's routing protocol daemon (rpd) causes improper handling of optional transitive BGP attributes. When the affected device receives a malformed BGP attribute over an existing session, it erroneously modifies the attribute before propagating it to peers. Peer devices then detect the malformed attribute and terminate their BGP sessions, causing availability impact through routing churn.

MitigationUpgrade Junos OS or Junos OS Evolved to the patched versions specified in the advisory (22.4R3-S8, 23.2R2-S5, 23.4R2-S6, 24.2R2-S2, or 24.4R2 and their Evolved equivalents).

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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 Junos version
    Run 'show version' or 'request system version' on the Juniper device to obtain the installed Junos OS or Junos OS Evolved version number
    Affected if The installed version matches < 22.4, = 22.4, = 23.2, = 23.4, = 24.2, or = 24.4 (any of the listed affected versions)
  2. Confirm BGP is enabled
    Run 'show bgp summary' or 'show protocols bgp' to verify BGP protocol is configured and active on the device
    Affected if BGP is configured and the device is participating in BGP peering sessions
  3. Verify rpd is running
    Run 'show system processes rpd' or check that the routing protocol daemon (rpd) is active
    Affected if The rpd process is running, which handles BGP attribute processing
  4. Check for BGP session flaps
    Run 'show bgp neighbor' and review logs for repeated BGP session resets or peer termination events
    Affected if Multiple BGP peers are terminating sessions unexpectedly, indicating potential attribute manipulation
  5. Review BGP attribute handling
    Examine BGP update messages using 'show bgp neighbor <peer> advertised' or capture BGP traffic to inspect optional transitive attributes
    Affected if Malformed attributes are being advertised to peers, causing peer session drops

A user is affected if the device runs a listed vulnerable Junos version AND has BGP peering sessions active, as the vulnerability triggers when processing malformed BGP attributes from peers.

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

Upgrade Junos OS or Junos OS Evolved to the patched versions specified in the advisory (22.4R3-S8, 23.2R2-S5, 23.4R2-S6, 24.2R2-S2, or 24.4R2 and their Evolved equivalents).

Recommended fix High confidence

22.4R3-S8 / 23.2R2-S5 / 23.4R2-S6 / 24.2R2-S2 / 24.4R2 (or -EVO variants for Evolved)

  1. 1. Identify the current Junos OS or Junos OS Evolved version running on the device using 'show version'
  2. 2. Determine which release train the device is on (22.4, 23.2, 23.4, 24.2, or 24.4)
  3. 3. For Junos OS devices on 22.4 train: upgrade to 22.4R3-S8 or later
  4. 4. For Junos OS devices on 23.2 train: upgrade to 23.2R2-S5 or later
  5. 5. For Junos OS devices on 23.4 train: upgrade to 23.4R2-S6 or later
  6. 6. For Junos OS devices on 24.2 train: upgrade to 24.2R2-S2 or later
  7. 7. For Junos OS devices on 24.4 train: upgrade to 24.4R2 or later
  8. 8. For Junos OS Evolved devices, use the corresponding -EVO suffix versions (22.4R3-S8-EVO, 23.2R2-S5-EVO, 23.4R2-S6-EVO, 24.2R2-S2-EVO, or 24.4R2-EVO)
Caveat Standard Junos upgrade considerations apply - review release notes for any behavior changes, ensure compatibility with other network devices, and test in lab environment first

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-60011 — 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-60011 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