CVE-2026-82312

LOWPre-NVD 1.81.8—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 1.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
1.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 1.8Exploit: None knownExposed: 0

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

OpenVPN 2.0.0 through 2.6.22 and 2.7_alpha1 through 2.7.6 on Windows allows local authenticated users to cause a denial of service via a NULL DACL on named IPC objects

CVSS v3
1.8
EG Score
1.8(medium)
EG Risk
8(Track)
EG Risk 8/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
Severity18% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

September 7, 2026

Last Modified

September 8, 2026

References (1)

Vendor Advisories for CVE-2026-82312(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 22× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 14:23 UTCEG score recompute
  3. 2026-09-18 14:23 UTCGHSA enrichment
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 08:13 UTCEG score recompute
  7. 2026-09-15 08:13 UTCGHSA enrichment
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-12 02:03 UTCEG score recompute
  11. 2026-09-12 02:03 UTCGHSA enrichment
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-08 22:01 UTCEPSS rescore
  15. 2026-09-08 19:53 UTCGHSA enrichment
  16. 2026-09-08 16:02 UTCEG score recompute
  17. 2026-09-08 16:02 UTCGHSA enrichment
  18. 2026-09-08 15:08 UTCEG score recompute
  19. 2026-09-08 15:07 UTCGHSA enrichment
  20. 2026-09-07 08:29 UTCEG score recompute
  21. 2026-09-07 07:53 UTCEG score recompute
  22. 2026-09-07 07:51 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-82312?
CVE-2026-82312 is a low vulnerability published on September 7, 2026. OpenVPN 2.0.0 through 2.6.22 and 2.7_alpha1 through 2.7.6 on Windows allows local authenticated users to cause a denial of service via a NULL DACL on named IPC objects
When was CVE-2026-82312 disclosed?
CVE-2026-82312 was first published in the National Vulnerability Database on September 7, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82312 actively exploited?
CVE-2026-82312 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 99.0% of all scored CVEs.
What is the CVSS score of CVE-2026-82312?
CVE-2026-82312 has a CVSS v3 base score of 1.8 (NVD).
How do I remediate CVE-2026-82312?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82312, 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-82312

Explore →

Is Your Infrastructure Affected by CVE-2026-82312?

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

Start Free Scan →Browse All CVEs