CVE-2026-40018

HIGHPre-NVD 7.47.4—
EchelonGraph scoreHIGH confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. a secondary CVSS source baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

None None None No publicly available exploits are known.

CVSS v3
7.4
EG Score
7.4(high)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Aug 28, 2026
No patch confirmed yet.
generic
https://documentation.open-xchange.com/dovecot/security/advisories/csaf/2026/oxdc-adv-2026-0003.json

Vendor Advisories for CVE-2026-40018(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 04:26 UTCEG score recompute
  2. 2026-08-30 04:26 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 16:32 UTCGHSA enrichment
  5. 2026-08-29 04:31 UTCGHSA enrichment
  6. 2026-08-28 16:36 UTCEG score recompute
  7. 2026-08-28 16:36 UTCGHSA enrichment
  8. 2026-08-28 15:39 UTCEG score recompute
  9. 2026-08-28 15:39 UTCGHSA enrichment
  10. 2026-08-28 12:23 UTCEG score recompute
  11. 2026-08-28 11:25 UTCEG score recompute
  12. 2026-08-28 11:19 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-40018?
CVE-2026-40018 is a high vulnerability published on August 28, 2026. None None None No publicly available exploits are known.
When was CVE-2026-40018 disclosed?
CVE-2026-40018 was first published in the National Vulnerability Database on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40018 actively exploited?
CVE-2026-40018 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.2% of all scored CVEs.
What is the CVSS score of CVE-2026-40018?
CVE-2026-40018 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-40018?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40018, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-40018

Explore →

Is Your Infrastructure Affected by CVE-2026-40018?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs