CVE-2025-24937: Nokia WaveSuite NOC · Vulnerability
Affects Nokia WaveSuite NOCSource CVE Database V5
Not known to be exploited · CVSS 9.0 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
AI-suggested
Organizations should immediately identify and inventory all instances of Nokia WaveSuite NOC, specifically versions 24.6, 23.6, and 23.12. Until a vendor patch is available, it is crucial to restrict network access to the WaveSuite NOC web interface by implementing strict firewall rules, allowing access only from trusted management networks and IP addresses. Employ network segmentation to isolate the NOC environment from general enterprise networks and the Internet. Monitor logs for unusual file access patterns or unexpected file modifications within the WaveSuite environment. Implement application-layer protections such as Web Application Firewalls (WAFs) configured to detect and block file inclusion attempts. Enforce the principle of least privilege for user accounts interacting with the NOC system to limit the potential for exploitation. Once Nokia releases a security patch, prioritize prompt testing and deployment. Additionally, conduct regular security assessments and penetration tests focusing on the NOC infrastructure to detect similar vulnerabilities proactively.
Description
File contents could be read from the local file system by an attacker. Additionally, malicious code could be inserted in the file, leading to a full compromise of the web application and the container it is running on. The vulnerable component is bound to the network stack and the set of possible attackers extends up to and including the entire Internet. The web application allows arbitrary files to be included in a file that was downloadable and executable by the web server.