dbcve.org
TerrascanApplication · Tenable

CVE-2026-47357

HIGH · 8.6 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to after 1.18.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Terrascan v1.18.3 and prior are vulnerable to Server-Side Request Forgery (SSRF) via the remote_url parameter in the remote directory scan endpoint (POST /v1/{iac}/{iacVersion}/{cloud}/remote/dir/scan) when running in server mode. An unauthenticated remote attacker can supply an attacker-controlled HTTP URL as remote_url with remote_type set to "http". The URL is passed directly to hashicorp/go-getter (v1.7.5) without validation. Go-getter's HttpGetter supports the X-Terraform-Get response header, allowing the attacker's server to redirect the download to a file:// URL, enabling local file read. Additionally, HttpGetter has Netrc set to true, causing it to read ~/.netrc and send stored credentials to attacker-controlled hostnames. This affects deployments running terrascan in server mode (terrascan server), which binds to 0.0.0.0 with no authentication. Note: Terrascan was archived in August 2023 and no patch will be released.

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 · high confidence

Terrascan v1.18.3 and prior contains an SSRF vulnerability in server mode where the remote_url parameter in POST /v1/{iac}/{iacVersion}/{cloud}/remote/dir/scan is passed unsanitized to hashicorp/go-getter v1.7.5. Attackers can redirect downloads from HTTP to file:// URLs to read local files, and go-getter's Netrc=true setting causes ~/.netrc credentials to be sent to attacker-controlled hosts.

MitigationDo not run Terrascan in server mode or ensure server is not exposed to untrusted networks (avoid binding to 0.0.0.0); consider migrating to an actively maintained alternative as Terrascan is archived.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TerrascanApplication
Affected:<= 1.18.3

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
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Check installed Terrascan version
    Run 'terrascan version' or check the binary version to confirm it is <= 1.18.3
    Affected if The installed version is 1.18.3 or lower
  2. Identify if Terrascan server mode is active
    Check running processes for 'terrascan server' or review systemd/service configurations for server mode startup
    Affected if Terrascan is running as a server (daemon mode) listening for API requests
  3. Verify server network exposure
    Check the listening port (default 9010) and whether it is bound to 0.0.0.0 or an exposed interface. Use 'netstat -tlnp' or 'ss -tlnp' to inspect the bind address
    Affected if The server is listening on a reachable network interface (not localhost only)
  4. Confirm outbound network access is permitted
    Review firewall rules or network policies allowing the Terrascan server process to make outbound HTTP/HTTPS connections
    Affected if The Terrascan server has the ability to initiate outbound network requests

You are affected if Terrascan version is 1.18.3 or lower AND server mode is active with network access, allowing unauthenticated remote directory scans via the remote_url parameter.

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
Upgrade available Upgrade to a release after 1.18.3
Interim mitigation

Do not run Terrascan in server mode or ensure server is not exposed to untrusted networks (avoid binding to 0.0.0.0); consider migrating to an actively maintained alternative as Terrascan is archived.

Recommended fix High confidence
  1. 1. Discontinue use of Terrascan in server mode (terrascan server) as no fix will be released.
  2. 2. If Terrascan is needed for local scanning only, use the CLI mode without the server component.
  3. 3. If server functionality is required, consider migrating to an actively maintained alternative IaC security scanning solution.
  4. 4. Ensure no Terrascan server instances are exposed to untrusted networks, as they are vulnerable to unauthenticated SSRF attacks.
  5. 5. Review and rotate any credentials stored in ~/.netrc that may have been exfiltrated if the server was previously compromised.
Caveat Terrascan was archived in August 2023 with no patch planned; migrating to an alternative solution is required

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

Fix this in Terrascan Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing2.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47357 — 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-47357 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