dbcve.org
TerrascanApplication · Tenable

CVE-2026-47356

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 webhook_url parameter in the file scan endpoint (POST /v1/{iac}/{iacVersion}/{cloud}/local/file/scan) when running in server mode. An unauthenticated remote attacker can supply an arbitrary URL as the webhook_url multipart form parameter. After scanning the uploaded file, Terrascan sends an HTTP POST request to the attacker-controlled URL containing the full scan results as a JSON body, with the attacker-supplied webhook_token forwarded as a Bearer token in the Authorization header. The retryable HTTP client retries up to 10 times on failure. 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 in its server mode. Attackers can supply an arbitrary URL via the webhook_url parameter, causing the server to POST scan results (containing full IaC configurations as JSON) to an attacker-controlled endpoint. The attacker-supplied webhook_token is also forwarded as a Bearer token in the Authorization header, enabling potential token leakage. The HTTP client retries up to 10 times, amplifying the impact.

MitigationSince Terrascan is archived with no patch forthcoming, immediately disable server mode or restrict network exposure (e.g., firewall/ACLs blocking 0.0.0.0 access). Consider migrating to actively maintained IaC scanning alternatives.

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' to determine the installed version
    Affected if Version is 1.18.3 or lower (the vulnerable version range)
  2. Verify Terrascan server is running
    Check for running Terrascan server processes (e.g., 'ps aux | grep terrascan') or look for the server port (default 9010) in use with 'netstat -tlnp' or 'ss -tlnp'
    Affected if Terrascan server process is actively running and listening on a network port
  3. Confirm server mode is enabled
    Review Terrascan configuration files or check the command used to start the server (look for 'server' subcommand or '-s' flag)
    Affected if Server mode was started with the 'server' subcommand or equivalent configuration
  4. Check network exposure of the Terrascan server
    Use 'netstat -tlnp' or 'ss -tlnp' to identify which network interfaces the Terrascan server port is bound to (0.0.0.0 indicates exposure)
    Affected if The server port is bound to 0.0.0.0 or an externally accessible IP address, allowing unauthenticated network access
  5. Inspect webhook configuration
    Review any Terrascan configuration files or environment variables for 'webhook_url' or 'webhook_token' settings that may have been used
    Affected if A custom webhook_url is configured, indicating the feature has been used and could have sent data to an attacker-controlled URL

You are affected if Terrascan version 1.18.3 or lower is installed AND the server mode is actively running and accessible on the network, allowing unauthenticated attackers to trigger the SSRF via the file scan endpoint.

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

Since Terrascan is archived with no patch forthcoming, immediately disable server mode or restrict network exposure (e.g., firewall/ACLs blocking 0.0.0.0 access). Consider migrating to actively maintained IaC scanning alternatives.

Recommended fix High confidence
  1. Do not run Terrascan in server mode (terrascan server) as it binds to 0.0.0.0 with no authentication.
  2. If server mode is required, implement network-level access controls such as firewall rules or network segmentation to restrict access to trusted sources only.
  3. Consider using Terrascan as a CLI tool instead of running the server.
  4. Monitor for any suspicious outbound HTTP requests from the Terrascan server process.

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

Fix this in Terrascan Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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