Security readout for executives and security teams
Plain-English summary
Ericsson Packet Core Controller versions before 1.38 contain a command-injection flaw that can let a sufficiently privileged attacker execute code with root control. Successful exploitation could compromise the controller’s confidentiality, integrity, and availability. Exposure is constrained by the adjacent-network and high-privilege requirements.
Executive priority
Treat this as an urgent, environment-dependent remediation item. Immediately determine whether PCC is deployed and whether any instance predates 1.38. Root execution creates severe operational risk, although adjacent access and high privileges reduce broad internet-scale exposure. Escalate affected production packet-core systems through emergency change review.
Technical view
CVE-2025-59172 is a CWE-78 OS command-injection vulnerability in Ericsson PCC before version 1.38. CVSS 4.0 rates it 8.5: adjacent-network access, low complexity, high privileges, no user interaction, and high local confidentiality, integrity, and availability impact. The supplied evidence does not identify the vulnerable interface or input path.
Likely exposure
Exposure is limited to Ericsson PCC deployments running versions earlier than 1.38. The attacker must reportedly have adjacent-network reachability and high privileges. The bundle’s structured affected-version entry is inconsistent, listing version “0” as unaffected, so organizations should verify applicability against Ericsson’s bulletin.
Exploitation context
The supplied sources do not report active exploitation, and the CVE is not identified as being in CISA’s KEV catalog. Exploitation requires high privileges but can yield root-level arbitrary code execution without user interaction. No public exploit availability or attack prevalence is established by this bundle.
Researcher notes
The CVSS vector indicates AV:A, AC:L, PR:H, UI:N, with high local confidentiality, integrity, and availability impacts and no subsequent-system impacts. The provided material does not disclose the affected command path, exploitation method, indicators, or patch mechanics. The structured affected data conflicts with the narrative version range and warrants vendor confirmation.
Mitigation direction
- Identify Ericsson PCC deployments and record their exact software versions.
- Prioritize systems running versions earlier than 1.38 for remediation review.
- Consult Ericsson’s security bulletin for supported upgrade instructions and deployment-specific precautions.
- Restrict PCC management access to necessary trusted networks and privileged administrators.
- Monitor privileged accounts and controller activity for unexpected changes.
Validation and detection
- Confirm each PCC instance reports version 1.38 or a later vendor-supported release.
- Compare deployed versions and configurations with Ericsson’s bulletin.
- Verify PCC management interfaces are unreachable from unauthorized or non-adjacent networks.
- Review privileged access records for anomalous sessions or administrative actions.
- Check controller logs and integrity monitoring for unexplained root-level activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-59172 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.5 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——ERICVulnerability scoring details
Base CVSS 4.0 score
8.5HighVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.ericsson.com/en/about-us/security/psirt/security-bulletin-pcc-july-2026CVE reference, ERIC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.