CVE-2025-7406
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 · uneditedNokia MantaRay NM is vulnerable to a sudo privilege escalation vulnerability where a local attacker possessing administrative (local admin) privileges can escalate to full root privileges on the host. Successful exploitation results in root-level access to the filesystem and the ability to execute actions as root. The risk can be temporarily mitigated by restricting the set of commands permitted via sudo for the affected accounts.
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 confidenceNokia MantaRay NM contains a sudo privilege escalation vulnerability where a local attacker with administrative privileges can execute commands as root by exploiting sudo configuration. The vulnerability allows a local admin user to bypass intended sudo restrictions and gain full root access to the host filesystem and execute privileged operations.
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< 25R2-NMCVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Nokia Mantaray Nm versionRun 'nm -v' or 'nm --version' from the command line, or check the package manager for the installed nm package versionAffected if The installed version is older than 25R2-NM (e.g., 25R1, 24R3, etc.)
-
Identify sudoers configuration fileInspect /etc/sudoers and any files in /etc/sudoers.d/ directory for nm user or admin group entriesAffected if The sudoers file contains entries that allow nm user or admin accounts to run commands as root without password or with overly broad command permissions (e.g., ALL=(ALL) ALL, or missing restrictions)
-
Check for unrestricted shell accessLook for sudo entries that permit execution of /bin/bash, /bin/sh, or other shell interpreters without full path restrictionsAffected if The sudoers configuration allows running shell interpreters as root without proper command path restrictions
-
Verify sudo command loggingCheck if sudo commands are being logged appropriately and review recent sudo execution history using 'sudo log' or reviewing /var/log/secure or /var/log/auth.logAffected if Sudo executions show commands being run as root by local admin users that should not have been permitted under least-privilege principles
The environment is affected if Nokia Mantaray Nm version is below 25R2-NM AND the sudoers configuration contains overly permissive rules that allow local admin users to execute arbitrary commands as root.
Generated from the published advisory. Verify against your own configuration.
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 · scoped25R2-NM
Restrict the set of commands permitted via sudo for affected accounts by reviewing and tightening the sudoers configuration to remove unnecessary sudo privileges that allow arbitrary command execution.
25R2-NM
- 1. Identify current MantaRay NM version by checking system information or running: mantaray-nm --version
- 2. Plan and schedule a maintenance window for the upgrade process
- 3. Perform a full backup of the MantaRay NM configuration following Nokia backup procedures
- 4. Download the fixed version (25R2-NM or later) from Nokia's official support portal
- 5. Upgrade the MantaRay NM installation to version 25R2-NM using Nokia's standard upgrade procedure
- 6. After upgrade, verify the new version is running: mantaray-nm --version
- 7. Confirm the sudo configuration no longer allows privilege escalation for administrative users
- 8. Test that normal administrative functions work correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7406 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7406 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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