dbcve.org
JunosOperating system · Juniper

CVE-2025-52958

MEDIUM · 5.3 CVSS v3.1 Published 2025-07-11
Fix available
A fix is available. Upgrade to 22.2 or later.
See remediation →
58/100
Remediation priority · Elevated
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
A Reachable Assertion vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent, unauthenticated attacker to cause a Denial of Service (DoS).On all Junos OS and Junos OS Evolved devices, when route validation is enabled, a rare condition during BGP initial session establishment can lead to an rpd crash and restart. This occurs specifically when the connection request fails during error-handling scenario. Continued session establishment failures leads to a sustained DoS condition.  This issue affects Junos OS: * All versions before 22.2R3-S6, * from 22.4 before 22.4R3-S6, * from 23.2 before 23.2R2-S3, * from 23.4 before 23.4R2-S4, * from 24.2 before 24.2R2; Junos OS Evolved: * All versions before 22.2R3-S6-EVO, * from 22.4 before 22.4R3-S6-EVO, * from 23.2 before 23.2R2-S3-EVO, * from 23.4 before 23.4R2-S4-EVO, * from 24.2 before 24.2R2-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 Reachable Assertion vulnerability in the routing protocol daemon (rpd) of Juniper Junos OS and Junos OS Evolved allows an adjacent, unauthenticated attacker to cause rpd to crash and restart during a rare error-handling condition during BGP initial session establishment when route validation is enabled. Repeated exploitation can lead to sustained DoS.

MitigationUpgrade Junos OS/Evolved to the patched versions specified (22.2R3-S6, 22.4R3-S6, 23.2R2-S3, 23.4R2-S4, 24.2R2 or respective -EVO equivalents). If upgrade is not immediately feasible, consider disabling route validation (routing-options validation) if not required, as a temporary workaround.

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
Junos Os EvolvedOperating system
Affected:< 22.2= 22.2= 22.4= 23.2= 23.4= 24.2

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
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:H/PR:N/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 installed Junos version
    Run `show version` or `show version detail` on the device CLI and note the exact version number (for example: 22.2R1, 22.4R3, 23.2R1, etc.)
    Affected if The installed version is 22.2, 22.4, 23.2, 23.4, 24.2, or any version lower than 22.2 (for example 21.4, 21.2, etc.)
  2. Confirm BGP is configured
    Run `show configuration protocols bgp` to see if BGP is configured on the device
    Affected if BGP is actively configured and the device participates in BGP peering
  3. Verify route validation is enabled
    Run `show configuration routing-options validation` or check the configuration for `set routing-options validation` statements under the validation hierarchy
    Affected if Route validation (also known as RPKI validation or routing-options validation) is explicitly enabled in the configuration
  4. Check device accessibility
    Review interface configurations and network exposure using `show configuration interfaces` and `show configuration protocols bgp group <name>` to identify which BGP peers are allowed
    Affected if The device accepts BGP connections from adjacent network segments (untrusted interfaces) without strict peer filtering

A device is affected if it runs an affected Junos/Evolved version AND has BGP configured AND has route validation (routing-options validation) enabled AND is accessible to adjacent attackers.

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

Upgrade Junos OS/Evolved to the patched versions specified (22.2R3-S6, 22.4R3-S6, 23.2R2-S3, 23.4R2-S4, 24.2R2 or respective -EVO equivalents). If upgrade is not immediately feasible, consider disabling route validation (routing-options validation) if not required, as a temporary workaround.

Recommended fix High confidence

Upgrade to Junos OS 24.2R2 or later (or Junos OS Evolved 24.2R2-EVO or later), or one of the SVR releases: 22.2R3-S6, 22.4R3-S6, 23.2R2-S3, or 23.4R2-S4

  1. 1. Identify the current Junos OS or Junos OS Evolved version installed on the device using 'show version' command.
  2. 2. Determine which version branch is currently running (22.2, 22.4, 23.2, 23.4, or 24.2).
  3. 3. For Junos OS: Upgrade to the appropriate fixed release based on your current branch: 22.2R3-S6 or later, 22.4R3-S6 or later, 23.2R2-S3 or later, 23.4R2-S4 or later, or 24.2R2 or later.
  4. 4. For Junos OS Evolved: Upgrade to 22.2R3-S6-EVO or later, 22.4R3-S6-EVO or later, 23.2R2-S3-EVO or later, 23.4R2-S4-EVO or later, or 24.2R2-EVO or later.
  5. 5. Prioritize the latest stable release (24.2R2 or later) to ensure all security patches are included.
  6. 6. After upgrade, verify the routing protocol daemon (rpd) is running stable using 'show system processes rpd'.
Caveat Review Juniper release notes for upgrade considerations; SVR releases contain additional fixes beyond standard major/minor releases

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