CVE-2026-18556
Exploitation confirmed. First attested on 2026-08-01 by CISA-ADP, CISA KEV, GCVE · kevintel.
- Published2026-08-01
- WeaknessCWE-288
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Authentication bypass using an alternate path or channel vulnerability in N-able N-central allows Authentication Bypass. This issue affects N-central: through 2026.1.
Timeline
dates in UTCObserved activity
isMalicious corpus · updated 2026-11-03 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-18556?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-18556?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2026.1 | ≤ 2026.1 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As N-able, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- N-able N-centralother versions: not affectedAffected
- ≤ 2026.1no fix statedcustom
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-08-01
Fix
- CISA’s 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 2026-08-07
Advisories and patches
- uptime.n-able.comVendor Advisory
- www.n-able.comVendor Advisory
Detection
read 2026-11-02 22:42 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 1 repository, unverifiedCreamyG31337/ncentral-compromise-ioc-triage PoC-in-GitHub
- Metasploit modules
- none listed Metasploit Framework
CISA Known Exploited Vulnerability
- Date Added
- 2026-08-04
- Patch Due Date
- 2026-08-07
- Ransomware Use
- Unknown
- 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.
Sources
- CISA KEVKEV entry2026-08-04
- ENISA EUVDexploitation2026-08-042026-08-04
- GCVEexploitation2026-08-01
- CISA-ADPSSVC decisionactive2026-08-04
- OpenCVESSVC decisionactive—
- CNACVSS 4.08.2known since 2026-10-24
- NVDCVSS 3.17.4read 2026-10-24
- CNAweakness (CWE)CWE-288known since 2026-10-24
- FIRST EPSSEPSS score7.9 %2026-11-03
- PoC-in-GitHubproof of concept1read 2026-11-02
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2026-51918same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-fffv-7w63-p3xwsame flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- CVSS 4.0 vector
- CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/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
- Published
- 2026-08-01
- Last Modified
- 2026-10-23
- NVD status
- Analyzed
- GitHub Advisory
- GHSA-fffv-7w63-p3xw
Frequently asked questions
What is CVE-2026-18556?
Is CVE-2026-18556 actively exploited?
What is the CVSS score for CVE-2026-18556?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CISA KEV · CC0-1.0 (cisagov/kev-data)
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GCVE · GCVE dump terms (preserve source attribution)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-fffv-7w63-p3xw
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OpenCVE · OpenCVE terms of service · terms restrict redistribution
- PoC-in-GitHub · CC0-1.0
- CISA Vulnrichment · CC0-1.0