dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-14468

HIGH · 7.7 CVSS v3.1 Published 2026-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
HashiCorp Terraform Enterprise contained an issue in its version control system (VCS) ingestion of registry modules that did not correctly enforce the intended boundary on packaged module content. This may allow an authenticated user to include files from outside the intended repository content in a module and then download them, potentially exposing sensitive files readable by the ingestion process. This vulnerability, CVE-2026-14468, is fixed in Terraform Enterprise v2.0.4 and v1.2.4.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a path traversal vulnerability in HashiCorp Terraform Enterprise's VCS module ingestion system. The system fails to properly enforce boundary constraints when packaging registry modules from VCS repositories, allowing authenticated users to reference files outside the intended repository content. These files can then be downloaded, potentially exposing sensitive files accessible to the ingestion process.

MitigationUpgrade Terraform Enterprise to v2.0.4, v1.2.4, or later fixed versions. Additionally, review access controls and audit logs for any suspicious module ingestion activity from the time before the patch was applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Terraform Enterprise version
    Access the Terraform Enterprise admin console or check the installed version through the /api/v1/version endpoint or the administrative UI. Compare the version number against the fixed releases v1.2.4 and v2.0.4.
    Affected if The installed version is earlier than v1.2.4 or v2.0.4 (or does not match a known fixed release).
  2. Verify VCS module ingestion is configured
    Check the Terraform Enterprise administrative settings for Registry module VCS providers. Look for configured VCS connections in the Module Registry settings under the Infrastructure menu.
    Affected if A VCS provider is connected and module ingestion from VCS repositories is enabled.
  3. Review module ingestion audit logs
    Access the Terraform Enterprise audit logs through the administrative UI or API. Filter logs for events related to module registry operations, specifically look for 'ModulePackage' or 'ModuleVersion' creation events.
    Affected if There are module ingestion events from VCS sources in the audit log, particularly where module paths may reference locations outside the repository.
  4. Inspect for anomalous module download patterns
    Examine the Terraform Enterprise logs for GET requests to module download endpoints. Look for requests to paths containing '../' sequences or non-repository paths in the module source field.
    Affected if Module download requests contain path traversal sequences or reference files outside the expected VCS repository structure.

A user is affected if they run Terraform Enterprise versions earlier than v1.2.4 or v2.0.4 with VCS module ingestion enabled, and either suspicious module ingestion activity appears in logs or anomalous download patterns are detected.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Terraform Enterprise to v2.0.4, v1.2.4, or later fixed versions. Additionally, review access controls and audit logs for any suspicious module ingestion activity from the time before the patch was applied.

Recommended fix High confidence

Terraform Enterprise v1.2.4 or v2.0.4

  1. 1. Identify current Terraform Enterprise version by checking the Admin UI or running the TFE diagnostics command
  2. 2. Create a complete backup of Terraform Enterprise data, including database and blob storage
  3. 3. Review Terraform Enterprise upgrade documentation for your current version
  4. 4. If running a version below v1.2.4 or v2.0.4, plan upgrade to either v1.2.4 (for legacy support) or v2.0.4 (latest stable release)
  5. 5. Test the upgrade in a non-production environment first to verify compatibility
  6. 6. Schedule maintenance window and apply the upgrade following HashiCorp upgrade procedures
  7. 7. After upgrade, verify the VCS module ingestion is working correctly
  8. 8. Confirm the fix by testing that path traversal is no longer possible in module ingestion
Caveat Review release notes for your current version before upgrading; major version upgrades may include configuration or API changes requiring adjustment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14468 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-14468 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data