Skip to main content
VulnerabilityPublished Updated

CVE-2025-59706: N2W · Authentication Bypass by Spoofing

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 4.4.1 : patch N2W as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Affects
N2W before 4.3.2
Patch
Available – fixed in 4.4.1, 4.3.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2025-59706, organizations should: 1) Immediately identify and inventory all N2W software instances and verify their versions. 3) Restrict API access using network segmentation, firewalls, and IP whitelisting to limit exposure to trusted sources only. 4) Implement strict API gateway validation and input sanitization to detect and block malformed requests. 5) Monitor logs and network traffic for unusual API activity indicative of exploitation attempts. 6) Employ intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalous API behavior. 7) Conduct regular security assessments and penetration testing focused on API endpoints. 8) Educate development and operations teams on secure API design and parameter validation best practices to prevent similar vulnerabilities. 9) Prepare incident response plans to quickly contain and remediate any exploitation. These measures collectively reduce the attack surface and improve detection and response capabilities.

Description

In N2W before 4.3.2 and 4.4.0 before 4.4.1, improper validation of API request parameters enables remote code execution.

References

Community reviews

Loading reviews…