CVE-2026-111943

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS
Trending — Patch released this week

Also known asEUVD-2026-106926 (ENISA EUVD)Source: ENISA EUVD

6.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return an error when calling Verify with any of the known intermediate certificates that are no longer considered to be trustworthy.

CVSS v3
6.8
EG Score
6.8MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity68% × 45%
Impact severity (EG Severity): CVSS 6.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.8): severity, escalated by confirmed exploitation. This CVE's 6.8 is its impact severity (EG Severity), not escalated.

EG Severity
6.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.CISA-ADP (Vulnrichment) CVSS v3.1 · CVSS v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 21, 2026

Last Modified

October 30, 2026

Advisory Details (5)

Auto-updated Oct 30, 2026
Patch available.
Web page

oss-security - Go 1.27.3 and Go 1.26.10 are released for CA certificate removal

http://www.openwall.com/lists/oss-security/2026/10/20/29
Web page

GO-2026-6809 - Go Packages

https://pkg.go.dev/vuln/GO-2026-6809
Web page

crypto/x509: mitigation for security concerns with a specific Certificate Authority · Issue #82345 · golang/go · GitHub

https://go.dev/issue/82345

Patch Availability(28)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatosbuild-composer-0:76.1-10.el9_22026-10-29redhat
redhatopenshift-service-mesh/istio-rhel9-operator:17929118432026-10-29redhat
redhatmicroshift-0:4.20.44-202610271817.p0.ge0d31e5.assembly.4.20.44.el92026-10-29redhat
redhatmicroshift-0:4.19.53-202610271823.p0.gb3195dc.assembly.4.19.53.el92026-10-29redhat
redhatignition-0:2.26.0-1.el9_8.22026-10-29redhat
redhatyggdrasil-worker-forwarder-0:0.1.1-1.el9sat2026-10-29redhat
redhatrhc-1:0.2.0-6.el8_4.22026-10-29redhat
redhatopenshift-service-mesh/istio-rhel9-operator:17929114642026-10-29redhat
redhatopenshift-service-mesh/istio-rhel9-operator:17929122422026-10-29redhat
redhatopenshift-service-mesh/istio-rhel9-operator:17929118542026-10-29redhat
redhatosbuild-composer-0:132.2-13.el9_62026-10-28redhat
redhatrhdh/rhdh-rhel9-operator:17931179722026-10-28redhat
redhatyggdrasil-0:0.4.7-6.el10_0.12026-10-28redhat
redhatignition-0:2.26.0-3.el10_2.42026-10-28redhat
redhatosbuild-composer-0:134.1-13.el10_02026-10-28redhat
redhatosbuild-composer-0:101.3-4.el9_4.72026-10-28redhat
redhatstf/sg-core-rhel9:17927601082026-10-28redhat
redhatignition-0:2.17.0-2.el9_4.32026-10-27redhat
redhatignition-0:2.15.0-2.el9_2.22026-10-27redhat
redhatrhc-1:0.2.2-1.el8_8.32026-10-27redhat
redhatgo-toolset:rhel8-8040020261027035356.522a0ee42026-10-27redhat
redhatose-gcp-gcr-image-credential-provider-0:4.22.0-202610221634.p2.g85bdbf8.assembly.stream.el82026-10-27redhat
redhatignition-0:2.16.2-6.rhaos4.14.el92026-10-27redhat
redhatskupper-cli-0:2.2.4-1.el92026-10-27redhat
redhatyggdrasil-0:0.4.9.2-1.el10_2.42026-10-27redhat
redhatose-gcp-gcr-image-credential-provider-0:4.20.0-202610221619.p2.gd4bfe3c.assembly.stream.el82026-10-27redhat
redhatrhc-1:0.2.1-14.el8_6.12026-10-27redhat
redhatgit-lfs-0:3.6.1-2.el10_0.82026-10-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 11× in last 7d / 27× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  4. 2026-10-30 13:33 UTCVendor advisory
  5. 2026-10-30 13:16 UTCEG score recomputeFirst assessed: 6.8 MEDIUM
  6. 2026-10-30 13:16 UTCVendor advisory
  7. 2026-10-30 13:15 UTCMITRE cvelistV5CVSS v3 → 6.8 · severity → MEDIUM
  8. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  9. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-10-25 14:51 UTCEG score recompute
  14. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-22 16:28 UTCEG score recompute
  18. 2026-10-22 16:28 UTCVendor advisory
  19. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-10-21 02:29 UTCVendor advisory
  21. 2026-10-21 02:25 UTCNVD update
  22. 2026-10-21 01:39 UTCVendor advisory
  23. 2026-10-21 01:37 UTCMITRE cvelistV5
  24. 2026-10-21 01:25 UTCNVD update
  25. 2026-10-21 01:18 UTCEG score recompute
Show 2 more
  1. 2026-10-21 01:18 UTCVendor advisory
  2. 2026-10-21 01:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-111943?
CVE-2026-111943 is a medium-severity vulnerability; its CVE record was published on October 21, 2026. On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return an error when…
When was the CVE record for CVE-2026-111943 published?
The CVE record for CVE-2026-111943 was published on October 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-111943 actively exploited?
CVE-2026-111943 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-111943?
CVE-2026-111943 has a CVSS v3.1 base score of 6.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-111943?
A fix for CVE-2026-111943 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-111943 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-111943?

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