Security readout for executives and security teams
Plain-English summary
Ericsson Packet Core Controller versions before 1.38 contain a credential embedded in the alarm system. Someone already able to access the cluster and possessing that credential could read alarm and alert information. The issue exposes operational confidentiality but is not described as enabling data changes, service disruption, or remote entry.
Executive priority
Schedule prompt remediation through normal vulnerability-management processes. Accelerate action where cluster access is weakly controlled or sensitive alarms could reveal operational conditions. This is not presented as an emergency internet-scale threat, but embedded credentials warrant attention because defenders cannot safely treat a shared secret as private.
Technical view
CVE-2025-59180 is a CWE-798 hard-coded credential weakness in PCC's alarm system. Exploitation requires cluster access and knowledge of the credential. CVSS 4.0 rates it 5.1: local attack vector, low complexity, no privileges or user interaction, and low vulnerable-system confidentiality impact only.
Likely exposure
Exposure is limited to Ericsson PCC deployments running versions earlier than 1.38. Risk is greatest where cluster access is broadly available, poorly segmented, or potentially compromised. The supplied affected-product metadata is inconsistent, so organizations should confirm exact applicability against Ericsson's bulletin and their deployed build.
Exploitation context
The bundle reports no CISA KEV listing and provides no evidence of active exploitation. Successful abuse requires both access to the PCC cluster and knowledge of the hard-coded credential, substantially limiting exposure compared with an internet-reachable vulnerability.
Researcher notes
The CVE description identifies PCC versions before 1.38, while the structured affected entry lists version "0" with default status unaffected. Treat that metadata conflict cautiously and defer to Ericsson's bulletin for authoritative version mapping. Available evidence supports read-only exposure of alarm and alert data; broader impact should not be inferred.
Mitigation direction
- Inventory PCC clusters and identify every deployed version.
- Prioritize upgrading versions earlier than 1.38 according to Ericsson's bulletin.
- Restrict cluster access to authorized administrators and trusted management networks.
- Review Ericsson guidance for any credential-specific remediation or additional safeguards.
Validation and detection
- Confirm each PCC cluster's exact version and whether it predates 1.38.
- Verify management and cluster access is appropriately restricted and segmented.
- Review access records for unexpected interaction with alarm or alert information.
- After remediation, confirm the deployed release is outside the stated affected range.
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-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access 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-59180 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
- 5.1 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/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:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N——ERICVulnerability scoring details
Base CVSS 4.0 score
5.1MediumVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/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.
Use of Hard-coded Credentials
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.