CVE-2025-24815: Nokia MantaRay NM File Upload Validation Flaw – Patch Guidance
Nokia MantaRay NM contains a file upload vulnerability that fails to properly validate uploaded file types. An authenticated user with local access could upload malicious files to the system, potentially leading to unauthorized code execution or system compromise. The vulnerability requires valid credentials but poses significant risk once an attacker is inside the network perimeter.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.8 HIGH · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses (CWE)
- CWE-434
- Affected products
- 1 configuration(s)
- Published / Modified
- 2026-06-30 / 2026-07-10
NVD description (verbatim)
Nokia MantaRay NM is subject to an unrestricted file upload vulnerability due to insufficient file type validation. Successful exploitation could allow an authenticated attacker to upload malicious files onto the system.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2025-24815 is a CWE-434 unrestricted file upload vulnerability in Nokia MantaRay NM. The application does not implement adequate file type validation on upload functionality, allowing an authenticated attacker with local access to bypass intended restrictions. The CVSS 3.1 score of 7.8 reflects high impact across confidentiality, integrity, and availability when successfully exploited. The attack vector is local, requiring prior authentication, but no user interaction is necessary once the upload mechanism is triggered.
Business impact
Successful exploitation could enable unauthorized file placement on critical network management infrastructure. Given MantaRay NM's role in telecom/carrier network operations, compromised file uploads could lead to service disruption, unauthorized configuration changes, or establishment of persistent backdoor access. The impact extends beyond the directly affected system to potentially encompass managed network assets. Organizations relying on MantaRay NM for network orchestration face operational continuity and security posture risks.
Affected systems
Nokia MantaRay NM is affected. Determine your specific version against Nokia's advisory to confirm applicability. MantaRay NM is commonly deployed in carrier and service provider environments for network management and orchestration. Environments with shared administrative access or where multiple operators interact with the platform warrant particular attention.
Exploitability
Exploitation requires valid system credentials and local access, which moderates the immediate external attack surface. However, insider threats, compromised accounts, or lateral movement from adjacent systems present realistic paths to exploitation. The absence of exploit code in public repositories at publication does not diminish the practical risk—insufficient file validation is a well-understood attack pattern. Organizations should assume exploitation difficulty is low for adversaries with authenticated access.
Remediation
Nokia has released patches addressing this vulnerability. Identify the patched version from the official Nokia security advisory and plan immediate deployment in your environment. Testing should confirm file upload restrictions are enforced. Parallel mitigations include restricting local system access through principle of least privilege, monitoring file upload activity, and disabling upload functionality if operationally feasible during patching.
Patch guidance
Consult Nokia's security advisory for the specific patched version applicable to your MantaRay NM deployment. Patches should be validated in a non-production environment before production rollout to ensure compatibility with your network management workflows. Establish a change window that minimizes disruption to managed network operations. After patching, verify that file type validation is functioning by testing upload restrictions with various file types.
Detection guidance
Monitor MantaRay NM logs for file upload activity, focusing on operations from authenticated users with unusual upload patterns or unexpected file types. Look for evidence of files persisting in unexpected directories. Network-level detection can target unusual file access or modification patterns on the system hosting MantaRay NM. Endpoint detection and response (EDR) tools should flag suspicious process execution originating from uploaded files. Audit logs should be reviewed for privilege escalation events following file uploads.
Why prioritize this
This vulnerability scores HIGH (7.8 CVSS) and requires immediate attention because: it affects network management infrastructure critical to carrier operations; successful exploitation grants file placement capability with integrity and availability impact; and the attack requires only authenticated local access, a realistic threat in environments with multiple operators. The absence of KEV designation does not diminish urgency—patch rapidly before adversaries develop weaponized proof-of-concepts targeting this common validation gap.
Risk score, explained
The CVSS 3.1 score of 7.8 (HIGH severity) reflects: local attack vector limiting initial exposure; requirement for low-privilege authentication reducing probability from fully unauthenticated attacks; but critically, high impact across all three security properties (confidentiality, integrity, availability) once access is achieved. File upload validation failures are straightforward to exploit for insiders and represent a direct path to code execution or persistent compromise.
Frequently asked questions
Does this vulnerability require internet access or can it only be exploited internally?
The vulnerability requires local access and valid credentials, meaning it cannot be exploited remotely over the internet. However, it can be exploited by insiders, through compromised accounts, or by attackers who have gained network access via other means. This makes it particularly relevant for supply chain security and insider threat scenarios.
What file types could an attacker upload to cause damage?
The vulnerability exists because file type validation is insufficient—this means executables, scripts, configuration files, or other malicious payloads could bypass intended restrictions. The specific impact depends on how MantaRay NM processes uploaded files and whether they are executed or parsed. Review Nokia's advisory for recommended file upload restrictions to implement after patching.
Is there a workaround if we cannot patch immediately?
Primary mitigations include: restricting local system access to MantaRay NM through strong access controls and multi-factor authentication; disabling file upload functionality if operationally possible; monitoring all file upload and system modification activity closely; and isolating MantaRay NM on a restricted network segment. These are not substitutes for patching but can reduce risk while patches are being staged.
Why isn't this vulnerability in the CISA KEV catalog despite the HIGH score?
KEV inclusion is based on evidence of active exploitation in the wild and is updated independently of CVSS scoring. A high CVSS score reflects severity, while KEV status reflects observed weaponization. The absence of KEV status means exploitation has not yet been widely observed, but this does not reduce the urgency of patching—patching before weaponization is discovered is always preferable.
This analysis is provided for informational and educational purposes to support security decision-making. All patch versions, CVSS scores, and remediation guidance should be verified against official Nokia security advisories before implementation. Organizations are responsible for assessing their specific environments and risk tolerance. This page does not constitute professional security advice; consult your security team and vendor guidance for your deployment. Source: NVD (public-domain), retrieved 2026-08-09. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2018-25388HIGHHaPe PKH 1.1 Arbitrary File Upload Vulnerability (CVSS 8.8)
- CVE-2018-25409HIGHSIM-PKH 2.4.1 Arbitrary File Upload Leading to Remote Code Execution
- CVE-2019-25758HIGHJoomla! vBizz Unrestricted File Upload to RCE
- CVE-2026-10072HIGHDreamMaker Arbitrary File Upload RCE Vulnerability
- CVE-2026-11344HIGHUnrestricted File Upload in code-projects Vehicle Management System 1.0
- CVE-2026-11419HIGHAltium Enterprise Server Path Traversal – Arbitrary File Write
- CVE-2026-11474HIGHUnrestricted File Upload in Kushan2k Student Management System
- CVE-2026-13430HIGHPost Export Import with Media Plugin Arbitrary File Upload (WordPress)