CVE-2026-3869

CRITICALPre-NVD 9.29.2
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 56% 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
9.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.2Exploit: None knownExposed: 0

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

CWE-303 : Incorrect Implementation of Authentication Algorithm vulnerability exists that could cause loss of confidentiality, integrity and availability of the PLC provided an application project with a lower application level is running on the PLC.

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

Published

September 11, 2026

Last Modified

September 18, 2026

Vendor Advisories for CVE-2026-3869(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 55× in last 7d / 64× 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-19 04:02 UTCGHSA enrichment
  2. 2026-09-18 23:47 UTCGHSA enrichment
  3. 2026-09-18 19:33 UTCEG score recompute
  4. 2026-09-18 19:33 UTCGHSA enrichment
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 19:28 UTCEPSS rescore
  7. 2026-09-18 16:46 UTCGHSA enrichment
  8. 2026-09-18 12:34 UTCGHSA enrichment
  9. 2026-09-18 08:21 UTCGHSA enrichment
  10. 2026-09-18 04:06 UTCGHSA enrichment
  11. 2026-09-17 23:54 UTCGHSA enrichment
  12. 2026-09-17 19:42 UTCEG score recompute
  13. 2026-09-17 19:42 UTCGHSA enrichment
  14. 2026-09-17 19:30 UTCEPSS rescore
  15. 2026-09-17 15:13 UTCGHSA enrichment
  16. 2026-09-17 11:01 UTCGHSA enrichment
  17. 2026-09-17 06:49 UTCGHSA enrichment
  18. 2026-09-17 02:36 UTCGHSA enrichment
  19. 2026-09-16 22:22 UTCGHSA enrichment
  20. 2026-09-16 18:06 UTCEG score recompute
  21. 2026-09-16 18:06 UTCGHSA enrichment
  22. 2026-09-16 14:08 UTCEPSS rescore
  23. 2026-09-16 13:51 UTCGHSA enrichment
  24. 2026-09-16 09:32 UTCGHSA enrichment
  25. 2026-09-16 05:19 UTCEG score recompute
Show 39 more
  1. 2026-09-16 05:19 UTCGHSA enrichment
  2. 2026-09-16 05:15 UTCEPSS rescore
  3. 2026-09-16 01:08 UTCGHSA enrichment
  4. 2026-09-15 20:56 UTCGHSA enrichment
  5. 2026-09-15 16:44 UTCGHSA enrichment
  6. 2026-09-15 12:32 UTCGHSA enrichment
  7. 2026-09-15 08:19 UTCGHSA enrichment
  8. 2026-09-15 04:07 UTCEG score recompute
  9. 2026-09-15 04:07 UTCGHSA enrichment
  10. 2026-09-15 03:11 UTCEPSS rescore
  11. 2026-09-14 23:55 UTCGHSA enrichment
  12. 2026-09-14 19:43 UTCGHSA enrichment
  13. 2026-09-14 15:31 UTCGHSA enrichment
  14. 2026-09-14 11:19 UTCGHSA enrichment
  15. 2026-09-14 07:07 UTCGHSA enrichment
  16. 2026-09-14 02:55 UTCGHSA enrichment
  17. 2026-09-13 22:43 UTCGHSA enrichment
  18. 2026-09-13 18:31 UTCEG score recompute
  19. 2026-09-13 18:31 UTCGHSA enrichment
  20. 2026-09-13 16:47 UTCEPSS rescore
  21. 2026-09-13 14:19 UTCGHSA enrichment
  22. 2026-09-13 10:07 UTCGHSA enrichment
  23. 2026-09-13 05:55 UTCGHSA enrichment
  24. 2026-09-13 01:43 UTCGHSA enrichment
  25. 2026-09-12 21:31 UTCGHSA enrichment
  26. 2026-09-12 17:19 UTCEG score recompute
  27. 2026-09-12 17:19 UTCGHSA enrichment
  28. 2026-09-12 15:01 UTCEPSS rescore
  29. 2026-09-12 13:07 UTCGHSA enrichment
  30. 2026-09-12 08:55 UTCGHSA enrichment
  31. 2026-09-12 04:41 UTCGHSA enrichment
  32. 2026-09-12 00:30 UTCGHSA enrichment
  33. 2026-09-11 20:18 UTCEG score recompute
  34. 2026-09-11 20:18 UTCGHSA enrichment
  35. 2026-09-11 19:19 UTCEG score recompute
  36. 2026-09-11 19:19 UTCGHSA enrichment
  37. 2026-09-11 16:30 UTCEG score recompute
  38. 2026-09-11 15:19 UTCEG score recompute
  39. 2026-09-11 15:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-3869?
CVE-2026-3869 is a critical vulnerability published on September 11, 2026. CWE-303 : Incorrect Implementation of Authentication Algorithm vulnerability exists that could cause loss of confidentiality, integrity and availability of the PLC provided an application project with a lower application level is running on the PLC.
When was CVE-2026-3869 disclosed?
CVE-2026-3869 was first published in the National Vulnerability Database on September 11, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3869 actively exploited?
CVE-2026-3869 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 55.5% of all scored CVEs.
What is the CVSS score of CVE-2026-3869?
CVE-2026-3869 has a CVSS v3 base score of 9.2 (NVD).
How do I remediate CVE-2026-3869?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3869, 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-3869

Explore →

Is Your Infrastructure Affected by CVE-2026-3869?

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