Is CVE-2026-47357 actively exploited?

No active exploitation of CVE-2026-47357 has been confirmed so far. Continue monitoring, as exploit status can change.

Can CVE-2026-47357 be exploited remotely?

Yes. CVE-2026-47357 is exploitable remotely over the network (CVSS attack vector: Network).

What is the CVSS score of CVE-2026-47357?

CVE-2026-47357 has a CVSS score of 8.6 (HIGH).

HOME VULNERABILITIESCVE-2026-47357

HIGH

CVE-2026-47357

CWE-73Published: May 19, 2026· Updated: May 20, 2026

8.6

CVSS v3.1

EPSS:0.04%probability of exploitation in 30 daysPercentile:11.1th

Official Description

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.

NVD Source

Technical Analysis

CVE-2026-47357 can be exploited remotely over the network without requiring physical or adjacent access, significantly expanding the attack surface for threat actors.

The vulnerability requires no privileges and no user interaction, making it a prime target for automated exploitation campaigns and worm-like propagation.

A successful exploit results in complete confidentiality breach (data exposure), with a CVSS base score of 8.6.

The vulnerability has a "Changed" scope, meaning successful exploitation can impact components beyond the vulnerable component itself — such as the host operating system or adjacent services.