CVE-2026-86218

N-central is vulnerable to a pre-auth remote code execution This issue affects N-central: before 2026.3.1.14.

Critical Known exploited

Severity: 10.0 / 10; Critical · CVSS 4.0
Exploit chance (EPSS): 15.38%; Chance of exploitation in the next 30 days. Higher than 96.78% of scored vulnerabilities.
Known exploited: Yes; In CISA's catalog since Sep 8, 2026
Weakness: CWE-96 Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')
Fix: None yet; No fixed version published

Exploited in the wild. N-able N-central Static Code Injection Vulnerability (N-able N-central). Required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Due for U.S. federal agencies by Sep 11, 2026.

Description

N-central is vulnerable to a pre-auth remote code execution This issue affects N-central: before 2026.3.1.14.

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 4.0 10.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack vector: Network
Attack complexity: Low
Attack requirements: None
Privileges required: None
User interaction: None
Confidentiality (vulnerable system): High
Integrity (vulnerable system): High
Availability (vulnerable system): High
Confidentiality (subsequent systems): High
Integrity (subsequent systems): High
Availability (subsequent systems): High
Exploit maturity: Not defined
Scope: X

CVSS 3.1 9.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Weakness

CWE-96: Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before inserting the input into an executable resource, such as a library, configuration file, or template.

How to prevent it

Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
Implementation: Perform proper output validation and escaping to neutralize all code syntax from data written to code files.

References

Advisories

me.n-able.com/s/security-advisory/aArVy0000002Ld3KAE/cve202686218-preauthenticatio…

Timeline

Sep 6, 2026 Published
Sep 8, 2026 Added to CISA's Known Exploited Vulnerabilities catalog
Sep 9, 2026 Last updated by the source
Sep 11, 2026 Remediation due for U.S. federal agencies
Nov 1, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-wcg9-pgqv-xm5v XWiki Platform allows XSS through XClass name in string properties	Medium	Same weakness, CWE-96
GHSA-w7w4-qjgg-372x Froxlor contains Static Code Injection	Medium	Same weakness, CWE-96
GHSA-x28w-hvwc-mp75 Static Code Injection in Microweber	High	Same weakness, CWE-96

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor