CVE-2025-59172 Ericsson CVE debrief

Who should care

Administrators and security teams responsible for Ericsson PCC systems should assess exposure and prioritize patching. This includes verifying PCC version and system configurations to prevent exploitation, monitoring system logs for suspicious activity, and planning vendor-supported updates or mitigations through normal change control where exposure is confirmed. Reviewing compensating controls for exposed systems is

Why it matters

CVE-2025-59172 is a high-severity vulnerability in Ericsson Packet Core Controller that allows arbitrary code execution as root. PCC administrators and security teams should assess exposure, prioritize patching, and monitor system logs.

• Potential for arbitrary code execution as root requires immediate attention and patching prioritization.
• Verification of PCC version and system configurations is necessary to prevent exploitation.
• Monitoring system logs for suspicious activity can help detect potential attacks.
• Remediation efforts should focus on updating PCC to version 1.38 or later.

Technical summary

The Ericsson Packet Core Controller (PCC) contains an Improper Neutralization of Special Elements vulnerability, allowing an attacker to execute arbitrary code as root. This issue affects PCC versions prior to 1.38. The vulnerability is considered high-severity and requires immediate attention. PCC administrators and security teams should assess exposure, prioritize patching, and monitor system logs for suspicious activity. The CVE record and NVD entry provide details on the vulnerability, but specific affected versions and remediation steps require verification.

Defensive priority

High priority for PCC administrators and security teams

Recommended defensive actions

• Verify PCC version and apply patch if necessary
• Review system configurations for potential vulnerabilities
• Monitor system logs for suspicious activity

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but specific affected versions and remediation steps require verification from Ericsson.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.