Previously, a user operating inside of a malicious Go project that defines a bogus golang.org/fips140 and operates a malicious GOMODPROXY the user chooses to connect to can serve an arbitrary module in its place. We now unpack the trusted ziphash for the bundled golang.org/fips140 module and construct its entry in the GOMODCACHE such that it can be verified by the toolchain.
CVE-2026-94444
UNRATEDCVSS · not yet scoredTrending — Patch released this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS v2: —Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- —
- EchelonGraph score
- Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
- EG Score
- —
- EG Risk
- —
- EPSS PROB
- 0.1%
- EPSS %ILE
- 1st
- KEV
- Not listed
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.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 8, 2026
Last Modified
October 9, 2026
References (4)
- security@golanghttps://go.dev/cl/840685
- security@golanghttps://go.dev/issue/81833
- security@golanghttps://groups.google.com/g/golang-announce/c/U2fTuyDJznI
- security@golanghttps://pkg.go.dev/vuln/GO-2026-6601
Vendor Advisories for CVE-2026-94444(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:79720Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- GHSA-2f4j-3hgj-v9j7GitHub Security Advisoriesunknown
Previously, a user operating inside of a malicious Go project that defines a bogus golang.org...
- RHSA-2026:79715Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | golang1-27-main-1.27.2-0.1.hum1 | 2026-10-08 | redhat |
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.
Affected Packages
(6 across 4 ecosystems)
Debian:14(3)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-1.25 | 1.25.0-1 ... 1.25.9-1 (20 versions) |
| — |
| golang-1.26 | 1.26.0-1 ... 1.26~rc3-2 (24 versions) |
| — |
| golang-1.27 | 1.27.0-1 ... 1.27~rc3-1 (9 versions) |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-1.19 | 1.19.10-1 ... 1.19.9-1 (12 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-1.24 | 1.24.12-1 ... 1.24.9-1 (10 versions) |
| — |
Go(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| toolchain | — |
| — |
Data Freshness Timeline
(refreshed 10× in last 7d / 10× 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.
- 2026-10-11 19:12 UTCEG score recompute
- 2026-10-11 16:27 UTCEG score recompute
- 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-11 13:40 UTCEG score recompute
- 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-09 17:01 UTCVendor advisory
- 2026-10-09 17:01 UTCGHSA enrichmentGHSA-2f4j-3hgj-v9j7
- 2026-10-08 23:20 UTCNVD update
- 2026-10-08 22:58 UTCEG score recompute
- 2026-10-08 22:58 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same vendor)
Same product
10 shownDebian:14:golang-1.27
Frequently asked(4)
What is CVE-2026-94444?
CVE-2026-94444 is a vulnerability whose severity is not yet rated; its CVE record was published on October 8, 2026. Previously, a user operating inside of a malicious Go project that defines a bogus golang.org/fips140 and operates a malicious GOMODPROXY the user chooses to connect to can serve an arbitrary module in its place. We now unpack the trusted ziphash for the bundled golang.org/fips140 module and…
When was the CVE record for CVE-2026-94444 published?
The CVE record for CVE-2026-94444 was published on October 8, 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 9, 2026; the record at its source may have been updated since.
Is CVE-2026-94444 actively exploited?
CVE-2026-94444 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-94444?
A fix for CVE-2026-94444 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-94444 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-94444
Is Your Infrastructure Affected by CVE-2026-94444?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.