Page generated: 06 Nov 2026, 03:51 UTC
← Dashboard

CVE-2026-111943

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 a…

Read full description
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 6.8 (MEDIUM)

Attention and evidence

HYPE SCORE
1.1/10
REALITY · THREAT PRIORITY
2.4/10
General review priority; not probability

Evidence confidence: Repository candidate

Why this priority?
  • Technical severity: CVSS 6.8: +2.38
  • Fresh EPSS: 0.40%: +0.01

General review priority, not probability, victim count or asset-specific risk. A range covers missing CVSS/EPSS inputs within the current evidence state.

Sources: 1 documents and public datasets.

Hype components

Headline sample (25%)
30/100
Press, 30 days (60%)
5/100
Grounded branding (15%)
0/100
HYPE TOTAL10/100

Sources and documents

Cisco Talos Blog
Press · 21 Oct 2026, 20:43 · Compromised eMudhra intermediate certificates

Score evolution

● Hype   ● Reality

Earlier evidence-support scores are retained in history; this chart shows only the current priority definition.

First record: hype 1.1 · reality 2.4 (2026-11-02 15:14). The curve appears once the score changes.

Public exploit evidence

1

Public exploit entries / repo candidates

See 1 repos with metrics
RepositoryStarsForksLanguageUpdated
abhishek-bhatkar/emudhra-poc51Python25 Oct 2026, 18:53
Evidence context and dated references

Reality is general threat/review priority, combining observed exploitation, CVSS severity and fresh EPSS. Evidence confidence is separate. This is not calibrated risk, a victim count or an asset-specific assessment. A range reflects missing numeric inputs. Published 16 days ago. Exploitation evidence usually takes weeks to show up: a low reality score can mean there is no data yet, not that the flaw is mild.

Evidence in context

Confidence in exploitation evidence
Repository candidate
Priority basis
Exploitation in attacks unconfirmed; CVSS 6.8; EPSS 0.4%
Attention, last 30 days
1 distinct story titles; 1 press documents; 1 publisher domains.
Technical potential
network access, no prior privileges, user interaction, additional attack conditions.
Observed activity
Public exploit repositories reference this CVE; none is corroborated.
Known scale
Not quantified.
Evidence confidence basis
Repository candidate; functionality unverified

Score evaluated: 2026-11-05 13:59:53.577903+00:00 · EPSS snapshot: 2026-11-05T12:03:04Z

Source event timeline
Published
21 Oct 2026, 00:52
First press mention
21 Oct 2026, 20:43
Latest press mention
21 Oct 2026, 20:43
Score calculated
05 Nov 2026, 13:59
PoCs on GitHub
1 repositories