Vulnerability in Terrascan (CVE-2026-47357)
Summary
Vulnerability in Terrascan (CVE-2026-47357). Confidential information can be exposed externally. Exploitable via POST /v1/{iac}/{iacVersion}/{cloud}/remote/dir/scan.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47357 has been found in Terrascan.
Attackers can target a specific entry point like POST /v1/{iac}/{iacVersion}/{cloud}/remote/dir/scan over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Terrascan CVE-2026-47357" on the vendor's site.
CVE-2026-47357 (Terrascan) — CWE-73 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /v1/{iac}/{iacVersion}/{cloud}/remote/dir/scan
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-73) exists in Terrascan. Attackers reach the vulnerable code path via POST /v1/{iac}/{iacVersion}/{cloud}/remote/dir/scan without authentication.
Check the vendor advisory for the affected versions of Terrascan. Attack surface: POST /v1/{iac}/{iacVersion}/{cloud}/remote/dir/scan.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /v1/{iac}/{iacVersion}/{cloud}/remote/dir/scan requests with malformed payloads or SQL meta-characters. Run grep -r 'Terrascan' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Terrascan' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Terrascanを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /v1/{iac}/{iacVersion}/{cloud}/remote/dir/scan' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /v1/{iac}/{iacVersion}/{cloud}/remote/dir/scanへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /v1/{iac}/{iacVersion}/{cloud}/remote/dir/scan on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web vulnreport@tenable.com
- web nvd.nist.gov
- web github.com