Skip to main content
VulnerabilityPublished Updated

CVE-2025-11700: N-able N-central · XML External Entity (XXE)

Affects N-able N-centralSource CVE Database V5

0

Public exploit available (Metasploit) · 31% EPSS · CVSS 8.4 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
31.6% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:L/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2025

  2. Weaponised: evidence found.

    1 Metasploit module

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

    Not in CISA KEV and no source reports exploitation

  4. 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

Affected software

ProductAffectedFixed in
N-able N-centralAffected
  • =0
Fixed in–

AI-suggested

To mitigate CVE-2025-11700, European organizations should take the following specific actions: 1) Immediately inventory all N-able N-central instances and verify their versions; prioritize those running versions earlier than 2025.4. 2) Apply vendor patches or updates as soon as they become available; monitor N-able security advisories closely. 3) If patches are not yet available, implement temporary mitigations such as disabling or restricting XML input processing features where feasible, or filtering and validating XML payloads at the network perimeter. 4) Restrict network access to N-central management interfaces to trusted IP addresses and enforce strong authentication and authorization controls to limit exposure. 5) Monitor logs and network traffic for anomalous XML requests or attempts to exploit XXE vulnerabilities. 6) Educate IT and security teams about the risks of XXE and ensure incident response plans include steps for detecting and responding to such attacks. 7) Consider deploying Web Application Firewalls (WAFs) with rules to detect and block malicious XML payloads targeting XXE patterns. These targeted mitigations go beyond generic advice by focusing on the specific attack vector and the operational context of N-central deployments.

Description

N-central versions < 2025.4 are vulnerable to multiple XML External Entities injection leading to information disclosure

References

Community reviews

Loading reviews…