# CVE-2025-59172: Improper Neutralization of Special Elements used in an OS Command Vulnerability

> Attackers can execute arbitrary code as root on Ericsson Packet Core Controller devices due to improper neutralization of OS command elements.

- **Severity:** High 8.5 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 27 Jul 2026
- **Updated:** 27 Jul 2026
- **Also known as:** GHSA-8j5f-6vjg-rf7w

## What is CVE-2025-59172?

CVE-2025-59172 is a high-severity command injection vulnerability in Ericsson Packet Core Controller (PCC), published on 27 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Ericsson Packet Core Controller (PCC) versions prior to 1.38 contain an Improper Neutralization of Special Elements vulnerability allowing an attacker to execute arbitrary code as root.

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

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


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

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

## Is CVE-2025-59172 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59172 is a high-severity command injection vulnerability in Ericsson Packet Core Controller (PCC), published on 27 Jul 2026. 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-59172 in the wild and no public exploit code.

Affected product: Ericsson Packet Core Controller (PCC). 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-59172/ (Markdown: https://insights.sbomify.com/CVE-2025-59172/index.md)
```

## Sources

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

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