CVE-2026-74797

LOWPre-NVD 3.13.1
EchelonGraph scoreHIGH confidence

Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-08-16. a secondary CVSS source baseline 3.1; sources differ by 0.0.

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

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

OpenTofu versions before 1.11.4 contain a denial of service vulnerability in the tofu init command when processing maliciously-crafted .zip archives for provider or module packages. Attackers can cause excessive CPU usage by controlling .zip archive content served during dependency installation, degrading system performance and preventing timely completion of the init process.

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

Published

August 16, 2026

Last Modified

August 17, 2026

Vendor Advisories for CVE-2026-74797(1)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/opentofu/opentofu1.11.4

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 14× 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-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 14:40 UTCEG score recompute
  3. 2026-08-20 14:40 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-18 13:49 UTCEPSS rescore
  6. 2026-08-18 13:49 UTCEPSS rescore
  7. 2026-08-17 18:31 UTCEG score recompute
  8. 2026-08-17 18:31 UTCGHSA enrichment
  9. 2026-08-17 18:00 UTCEG score recompute
  10. 2026-08-17 18:00 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 14:36 UTCEG score recompute
  13. 2026-08-16 13:27 UTCEG score recompute
  14. 2026-08-16 13:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74797?
CVE-2026-74797 is a low vulnerability published on August 16, 2026. OpenTofu versions before 1.11.4 contain a denial of service vulnerability in the tofu init command when processing maliciously-crafted .zip archives for provider or module packages. Attackers can cause excessive CPU usage by controlling .zip archive content served during dependency installation,…
When was CVE-2026-74797 disclosed?
CVE-2026-74797 was first published in the National Vulnerability Database on August 16, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74797 actively exploited?
CVE-2026-74797 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 92.8% of all scored CVEs.
What is the CVSS score of CVE-2026-74797?
CVE-2026-74797 has a CVSS v3 base score of 3.1 (NVD).
How do I remediate CVE-2026-74797?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74797, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-74797

Explore →

Is Your Infrastructure Affected by CVE-2026-74797?

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