# CVE-2025-52988: Junos OS and Junos OS Evolved: Privilege escalation to root via CLI command 'request system logout'

> A local high-privileged attacker can escalate to root via OS command injection in the 'request system logout' CLI command on Juniper devices.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/AU:Y/R:U/RE:M`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-w3xh-4xq9-g5fm

## What is CVE-2025-52988?

CVE-2025-52988 is a high-severity command injection vulnerability in Juniper Junos, published on 11 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in the CLI of Juniper Networks Junos OS and Junos OS Evolved allows a high privileged, local attacker to escalated their privileges to root.

When a user provides specifically crafted arguments to the 'request system logout' command, these will be executed as root on the shell, which can completely compromise the device.
This issue affects:

Junos OS: 

  *  all versions before 21.2R3-S9,
  *  21.4 versions before 21.4R3-S8,
  *  22.2 versions before 22.2R3-S6,
  *  22.3 versions before 22.3R3-S3,
  *  22.4 versions before 22.4R3-S6,
  *  23.2 versions before 23.2R2-S1,
  *  23.4 versions before 23.4R1-S2, 23.4R2;

Junos OS Evolved:

  *  all versions before 22.4R3-S6-EVO,
  *  23.2-EVO versions before 23.2R2-S1-EVO,
  *  23.4-EVO versions before 23.4R1-S2-EVO, 23.4R2-EVO.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 2 products.


Products: Juniper Junos, Juniper Junos Os Evolved.

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

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

## Is CVE-2025-52988 being exploited?

There is no known exploitation of CVE-2025-52988 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-52988 and fix it if it is affected.

What it is: CVE-2025-52988 is a high-severity command injection vulnerability in Juniper Junos, published on 11 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52988 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-52988/ (Markdown: https://insights.sbomify.com/CVE-2025-52988/index.md)
```

## Sources

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

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