dbcve.org
TerrascanApplication · Tenable

CVE-2026-47358

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 external URL resolution in uploaded IaC templates when running in server mode. When Terrascan parses uploaded ARM templates or CloudFormation templates, it resolves external URLs referenced within those templates via hashicorp/go-getter with all default detectors enabled, including FileDetector. An unauthenticated remote attacker can upload an ARM template containing a templateLink.uri or parametersLink.uri field, or a CloudFormation template containing an AWS::CloudFormation::Stack TemplateURL field, pointing to an attacker-controlled URL. Terrascan will fetch the attacker-controlled URL server-side. Unlike SSRF via the remote scan endpoint, file:// URLs are directly usable without requiring an X-Terraform-Get redirect, enabling local file read. 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 unauthenticated SSRF vulnerability when running in server mode. Attackers can upload ARM or CloudFormation templates containing malicious templateLink.uri, parametersLink.uri, or TemplateURL fields pointing to attacker-controlled URLs. Terrascan fetches these URLs server-side using hashicorp/go-getter with FileDetector enabled, allowing file:// URLs to read local files directly without requiring redirect handling. The server binds to 0.0.0.0 with no authentication.

MitigationDisable Terrascan server mode entirely or restrict network exposure; since Terrascan is archived with no patch, migrate to an actively-maintained alternative IaC scanner or implement upstream filtering to block template files containing external URL references before they reach Terrascan.

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 Terrascan version
    Run 'terrascan version' or check the installed binary version
    Affected if Version is 1.18.3 or lower
  2. Verify if server mode is in use
    Check running processes or deployment configuration for 'terrascan server' command, or review if the server port (default 9010) is listening
    Affected if Terrascan is running in server mode (terrascan server command)
  3. Confirm network binding configuration
    Inspect the server process for binding address - Terrascan server defaults to binding to 0.0.0.0
    Affected if Server is bound to 0.0.0.0 and accessible from network interfaces
  4. Check for ARM or CloudFormation template scanning
    Review logs, API requests, or configuration to see if templateLink.uri, parametersLink.uri (ARM), or AWS::CloudFormation::Stack TemplateURL (CloudFormation) templates are being submitted
    Affected if ARM templates with templateLink.uri/parametersLink.uri or CloudFormation templates with TemplateURL are being processed by the server

User is affected if running Terrascan <= 1.18.3 in server mode, bound to 0.0.0.0, and processing ARM or CloudFormation templates with external URL references

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

Disable Terrascan server mode entirely or restrict network exposure; since Terrascan is archived with no patch, migrate to an actively-maintained alternative IaC scanner or implement upstream filtering to block template files containing external URL references before they reach Terrascan.

Recommended fix High confidence
  1. Do not run Terrascan in server mode (terrascan server) as it has no authentication and is vulnerable to SSRF
  2. If server mode is required, bind to localhost only (127.0.0.1) instead of 0.0.0.0 using the appropriate server configuration flag
  3. Implement network-level firewall rules to prevent the Terrascan server from making arbitrary outbound network requests
  4. If running Terrascan server is not essential, use CLI mode (terrascan scan) instead which does not expose the SSRF attack surface
  5. Disable or restrict the FileDetector in hashicorp/go-getter configuration if possible, though this may require code modifications
Caveat No upgrade available - Terrascan was archived in August 2023 and no patch will be released

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

Fix this in Terrascan Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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