Network ManagerApplication · Ericsson

CVE-2025-27258

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-13
Fix available
A fix is available. Upgrade to 25.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Ericsson Network Manager (ENM) versions prior to ENM 25.1 GA contain a vulnerability, if exploited, can result in an escalation of privilege.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Ericsson Network Manager (ENM) versions prior to 25.1 GA contain a privilege escalation vulnerability allowing an attacker to gain higher-level access than originally provided. The critical CVSS score of 9.8 indicates this can likely be exploited remotely without authentication, potentially giving administrative control over the network management system.

MitigationUpgrade Ericsson Network Manager to version 25.1 GA or later. Prior to upgrade, restrict network exposure of ENM interfaces and implement strong access controls to reduce attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Network ManagerApplication
Affected:< 25.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify ENM version
    Log into the Ericsson Network Manager CLI or web interface and navigate to the version or system information section. Alternatively, run the command 'enmpkg -l' or check '/opt/enm/version' if such paths are standard on your system.
    Affected if The displayed version is any build prior to 25.1 GA (for example, 24.x, 23.x, or earlier).
  2. Verify management interface exposure
    Review your network configuration to determine whether ENM management ports (typically HTTPS ports 443, 8443, or proprietary ENM ports) are accessible from untrusted networks or the public internet. Use firewall rules or network scans to confirm external accessibility.
    Affected if The ENM web interface or CLI ports are reachable from outside your trusted network without VPN or jump host restrictions.
  3. Confirm user authentication settings
    Check the ENM user directory configuration to see which authentication mechanisms are enabled (local accounts, LDAP, TACACS+, RADIUS). Review whether default administrative accounts still exist with default credentials.
    Affected if Multiple authentication methods are enabled simultaneously, or default admin accounts with unchanged passwords are present in the system.

You are affected if your Ericsson Network Manager installation shows a version number below 25.1 GA and the management interface is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 25.1 or later
Fixed in 25.1
Interim mitigation

Upgrade Ericsson Network Manager to version 25.1 GA or later. Prior to upgrade, restrict network exposure of ENM interfaces and implement strong access controls to reduce attack surface.

Recommended fix High confidence

ENM 25.1 GA

  1. 1. Contact Ericsson support or access the Ericsson support portal to obtain the ENM 25.1 GA upgrade package
  2. 2. Follow Ericsson's official upgrade documentation and procedures for Ericsson Network Manager
  3. 3. Upgrade your ENM deployment to version 25.1 GA
  4. 4. Verify the upgrade was successful and the vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Network Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27258 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27258 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data