Skip to main content
VulnerabilityPublished Updated

CVE-2025-59707: 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-59707, organizations should: 1) Monitor official N2W communications and apply security patches immediately upon release for versions 4.3.2 and 4.4.1 or later. 2) Restrict network access to N2W management interfaces and services using firewalls, VPNs, or zero-trust network segmentation to limit exposure to untrusted networks. 3) Implement strong authentication mechanisms and multi-factor authentication to reduce the risk of credential theft exploitation. 4) Conduct regular audits of account activity and system logs to detect suspicious authentication attempts or anomalous code execution behaviors. 5) Employ intrusion detection and prevention systems (IDS/IPS) with signatures or heuristics targeting spoofing and remote code execution patterns relevant to N2W. 6) Educate IT and security teams on the specifics of this vulnerability to enhance incident response readiness. 7) Consider deploying application-layer gateways or proxies that can validate and filter traffic to N2W services. These steps go beyond generic patching by focusing on layered defenses and proactive monitoring to reduce attack surface and detect exploitation attempts early.

Description

In N2W before 4.3.2 and 4.4.x before 4.4.1, there is potential remote code execution and account credentials theft because of a spoofing vulnerability.

References

Community reviews

Loading reviews…