Security readout for executives and security teams
Plain-English summary
Ericsson Packet Core Controller versions before 1.39 contain a directory traversal flaw in Configuration Management. A highly privileged attacker on an adjacent network could alter directory permissions, blocking legitimate users and disrupting administration. The supplied severity is medium, with limited integrity and availability impact.
Executive priority
Handle through the normal vulnerability-remediation cycle, accelerating systems running pre-1.39 releases or supporting sensitive packet-core operations. The required privilege and adjacent access reduce urgency, but permission changes could disrupt legitimate administration. Confirm ownership, exposure, and vendor remediation promptly.
Technical view
CVE-2025-59181 is classified as CWE-35 and scored 4.8 under CVSS v4.0. The vector requires adjacent-network access and high privileges, with low attack complexity, no user interaction, and low integrity and availability impact. The reported capability is changing directory permissions; broader file access is not established.
Likely exposure
Exposure is likely limited to organizations operating Ericsson PCC releases earlier than 1.39 where privileged Configuration Management access is reachable from an adjacent network. Internet reachability is not supported by the supplied vector. The structured affected-version data is ambiguous, so operators should confirm applicability with Ericsson.
Exploitation context
The source bundle provides no evidence of active exploitation, and the CVE is not identified as KEV. Exploitation requires high privileges and adjacent-network access, reducing broad opportunistic risk. A compromised administrator account or trusted management segment could still make the flaw operationally significant.
Researcher notes
The bundle’s narrative identifies versions before 1.39, while its structured affected entry lists version “0” and default status “unaffected.” Confirm version applicability with Ericsson before drawing fleet-wide conclusions. Evidence supports directory-permission modification and denial of legitimate access only; arbitrary file disclosure, remote code execution, and public exploitation are not established.
Mitigation direction
- Review Ericsson’s bulletin and apply its supported update or mitigation for PCC versions before 1.39.
- Until remediated, restrict Configuration Management access to necessary administrators and trusted adjacent networks.
- Monitor directory permissions and restore approved settings if unauthorized changes are detected.
Validation and detection
- Inventory PCC deployments and flag versions earlier than 1.39 for review.
- Confirm exact affected versions and remediation requirements against Ericsson’s security bulletin.
- Review Configuration Management reachability, segmentation, and assignment of high-privilege accounts.
- Compare relevant directory permissions with approved baselines and investigate unexplained changes.
- After remediation, verify the installed version and recheck directory permissions and legitimate-user access.
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-35: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection 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 lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-59181 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
- Medium
- CVSS
- 4.8 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/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:N/VI:L/VA:L/SC:N/SI:N/SA:N——ERICVulnerability scoring details
Base CVSS 4.0 score
4.8MediumVector: CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/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.
Path Traversal: '.../...//'
Path Traversal: '.../...//' represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.