dbcve.org
JunosOperating system · Juniper

CVE-2025-60010

MEDIUM · 5.4 CVSS v3.1 Developing Published 2025-10-09
Fix available
A fix is available. Upgrade to 22.4 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 password aging vulnerability in the RADIUS client of Juniper Networks Junos OS and Junos OS Evolved allows an authenticated, network-based attacker to access the device without enforcing the required password change. Affected devices allow logins by users for whom the RADIUS server has responded with a reject and required the user to change the password as their password was expired. Therefore the policy mandating the password change is not enforced. This does not allow users to login with a wrong password, but only with the correct but expired one. This issue affects: Junos OS:  * all versions before 22.4R3-S8, * 23.2 versions before 23.2R2-S4, * 23.4 versions before 23.4R2-S5, * 24.2 versions before 24.2R2-S1, * 24.4 versions before 24.4R1-S3, 24.4R2; Junos OS Evolved: * all versions before 22.4R3-S8-EVO, * 23.2 versions before 23.2R2-S4-EVO, * 23.4 versions before 23.4R2-S5-EVO, * 24.2 versions before 24.2R2-S1-EVO, * 24.4 versions before 24.4R1-S3-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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-07-31.

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

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

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
Recommended fix High confidence

Upgrade to Junos OS 22.4R3-S8/23.2R2-S4/23.4R2-S5/24.2R2-S1/24.4R1-S3/24.4R2 or later, or Junos OS Evolved 22.4R3-S8-EVO/23.2R2-S4-EVO/23.4R2-S5-EVO/24.2R2-S1-EVO/24.4R1-S3-EVO/24.4R2-EVO or later

  1. 1. Identify the current Junos OS or Junos OS Evolved version running on the device using 'show version' command.
  2. 2. Determine which release train (22.4, 23.2, 23.4, 24.2, or 24.4) the current version belongs to.
  3. 3. For Junos OS: upgrade to 22.4R3-S8 or later, 23.2R2-S4 or later, 23.4R2-S5 or later, 24.2R2-S1 or later, or 24.4R1-S3/24.4R2 or later depending on your release train.
  4. 4. For Junos OS Evolved: upgrade to 22.4R3-S8-EVO or later, 23.2R2-S4-EVO or later, 23.4R2-S5-EVO or later, 24.2R2-S1-EVO or later, or 24.4R1-S3-EVO/24.4R2-EVO or later depending on your release train.
  5. 5. Download the appropriate Junos software image from the Juniper Networks support portal (supportportal.juniper.net).
  6. 6. Transfer the software image to the device and verify the integrity using the provided checksums.
  7. 7. Install the upgrade using the 'request system software add <package-name>' command.
  8. 8. Reboot the device using 'request system reboot' command.
Caveat Standard Junos upgrade risks apply - ensure configuration backup before upgrade and plan for potential downtime; some older hardware platforms may have specific compatibility considerations

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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