# CVE-2025-59177: Generation of Error Message Containing Sensitive Information Vulnerability

> Attackers can reveal system secrets via crafted commands in error messages, requiring upgrades to secure Ericsson Packet Core Controllers.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/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-qh6w-fr9v-2742

## What is CVE-2025-59177?

CVE-2025-59177 is a medium-severity 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.39 contain a vulnerability in Configuration Management, allowing an attacker to execute specifically crafted commands to reveal system secret through error messages.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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


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

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

## Is CVE-2025-59177 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59177 is a medium-severity 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-59177 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-59177/ (Markdown: https://insights.sbomify.com/CVE-2025-59177/index.md)
```

## Sources

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

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