Ericsson Packet Core Controller (PCC) versions prior to 1.38 contain a hardcoded credential vulnerability in the alarm system. An attacker with access to the cluster with knowledge of the hardcoded credential can read alarm and alert information.
CVE-2025-59180
This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.1
- EG Score
- 5.1(medium)
- EG Risk
- 27(Track)EG Risk 27/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity51% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 2%
- KEV
- Not listed
Published
July 27, 2026
Last Modified
July 28, 2026
References (1)
- 85b1779b-6ecd-4f52-bcc5-73eac4659dcfhttps://www.ericsson.com/en/about-us/security/psirt/security-bulletin-pcc-july-2026
Vendor Advisories for CVE-2025-59180(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-28 16:30 UTCEG score recompute
- 2026-07-28 16:30 UTCGHSA enrichment
- 2026-07-28 15:35 UTCEPSS rescore
- 2026-07-27 16:24 UTCGHSA enrichment
- 2026-07-27 15:22 UTCEG score recompute
- 2026-07-27 14:26 UTCEG score recompute
- 2026-07-27 14:25 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-798
Frequently asked(5)
What is CVE-2025-59180?
When was CVE-2025-59180 disclosed?
Is CVE-2025-59180 actively exploited?
What is the CVSS score of CVE-2025-59180?
How do I remediate CVE-2025-59180?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-59180
Is Your Infrastructure Affected by CVE-2025-59180?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.