# CVE-2025-60010: Junos OS and Junos OS Evolved: Device allows login for user with expired password

> Attackers can bypass password expiration policies on Juniper devices, allowing access with expired but valid credentials.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/RE:M`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2025
- **Updated:** 9 Oct 2025
- **Also known as:** GHSA-7r8r-6vw9-6mf8

## What is CVE-2025-60010?

CVE-2025-60010 is a medium-severity authentication bypass vulnerability in Juniper Junos, published on 9 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-262 (Not Using Password Aging)

## Which versions are affected by CVE-2025-60010?

It affects 2 products.


Products: Juniper Junos, Juniper Junos Os Evolved.

## How do I fix CVE-2025-60010?

No fix has been published for CVE-2025-60010 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-60010 being exploited?

There is no known exploitation of CVE-2025-60010 in the wild and no public exploit code.

## Other vulnerabilities in Juniper Junos

- [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild)
- [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild)
- [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild)
- [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild)
- [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-60010 and fix it if it is affected.

What it is: CVE-2025-60010 is a medium-severity authentication bypass vulnerability in Juniper Junos, published on 9 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-60010 in the wild and no public exploit code.

Affected product: Juniper Junos. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-60010/ (Markdown: https://insights.sbomify.com/CVE-2025-60010/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-60010
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-60010
- OSV: https://osv.dev/vulnerability/CVE-2025-60010

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-60010/
Summaries are generated and may contain mistakes; the official description above is the record.