CVE-2026-74796

MEDIUMPre-NVD 6.16.1—
EchelonGraph scoreHIGH confidence

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

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

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

OpenTofu before 1.11.7 fails to validate existing symlinks in the provider cache directory during initialization. Attackers can place a malicious symlink in a trusted working directory to cause tofu init to write provider package contents to arbitrary filesystem locations outside the working tree.

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

Published

August 16, 2026

Last Modified

August 17, 2026

Advisory Details (2)

Auto-updated Aug 16, 2026
Patch available. Sources: github.
generic

OpenTofu before 1.11.7 Symlink Following Path Traversal | Advisories | VulnCheck

https://www.vulncheck.com/advisories/opentofu-before-symlink-following-path-traversal
github Patch Available

Provider cache installation follows root-module-controlled package directory symlink and writes outside the working tree · Advisory · opentofu/opentofu · GitHub

https://github.com/opentofu/opentofu/security/advisories/GHSA-wcmj-x466-56mm

Vendor Advisories for CVE-2026-74796(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/opentofu—1.11.7—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 19× 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 18:50 UTCGHSA enrichment
  3. 2026-08-19 18:21 UTCEG score recompute
  4. 2026-08-19 18:21 UTCGHSA enrichment
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-18 16:59 UTCEG score recompute
  7. 2026-08-18 16:59 UTCGHSA enrichment
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-17 16:24 UTCEG score recompute
  11. 2026-08-17 16:24 UTCGHSA enrichment
  12. 2026-08-17 16:11 UTCEG score recompute
  13. 2026-08-17 16:11 UTCGHSA enrichment
  14. 2026-08-17 15:05 UTCEG score recompute
  15. 2026-08-17 15:05 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-16 14:36 UTCEG score recompute
  18. 2026-08-16 13:27 UTCEG score recompute
  19. 2026-08-16 13:26 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-74796?
CVE-2026-74796 is a medium vulnerability published on August 16, 2026. OpenTofu before 1.11.7 fails to validate existing symlinks in the provider cache directory during initialization. Attackers can place a malicious symlink in a trusted working directory to cause tofu init to write provider package contents to arbitrary filesystem locations outside the working tree.
When was CVE-2026-74796 disclosed?
CVE-2026-74796 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-74796 actively exploited?
CVE-2026-74796 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 86.0% of all scored CVEs.
What is the CVSS score of CVE-2026-74796?
CVE-2026-74796 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-74796?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74796, 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-74796

Explore →

Is Your Infrastructure Affected by CVE-2026-74796?

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

Start Free Scan →Browse All CVEs