Skip to content
Fencer Vulns
critical 9.8

CVE-2026-86218 kev in the critical feed json

pre-authentication remote code execution

published 2026-09-06 2 mo ago modified 2026-09-09 2 mo ago also EUVD-2026-72041

cvss
9.8
version 3.1, NVD
cisa kev
Exploited
added 2026-09-08
epss
15.4%
EPSS 15.4% chance of exploitation in 30 days, percentile 96%
public exploits
1
Metasploit, plus a Nuclei check

Summary

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

Patch / fix

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

  • N-able N-central 2026.3.1.14

Timeline

  1. First public exploit (Metasploit exploit/linux/http/nable_ncentral_unauth_rce_cve_2026_86218)
  2. Published
  3. CISA SSVC: exploitation active
  4. Added to CISA KEV
  5. CISA patch deadline

Known exploited

Added
2 mo ago
Patch by
2026-09-11 (59 d ago)
Ransomware
Not known
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.
Vendor, product
N-able, N-central
CISA name
N-able N-central Static Code Injection Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
yes
Technical impact
total
Assessed
2 mo ago

Exploit prediction

15.38% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 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
CNA 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
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • N-able N-central

Classification

Weakness
  • CWE-96 Improper Neutralization of Directives in Statically Saved Code

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.