# CVE-2026-47356: Server-side request forgery in Terrascan

> Unauthenticated attackers can force Terrascan server to send scan results to arbitrary URLs via SSRF in webhook configuration.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2026
- **Updated:** 19 May 2026
- **Also known as:** GHSA-q2p7-5m6x-29x8

## What is CVE-2026-47356?

CVE-2026-47356 is a high-severity server-side request forgery vulnerability in tenable Terrascan, published on 19 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-47356?

It affects 1 product.


Products: Tenable Terrascan.

## How do I fix CVE-2026-47356?

No fix has been published for CVE-2026-47356 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47356 being exploited?

There is no known exploitation of CVE-2026-47356 in the wild and no public exploit code.

## Other vulnerabilities in tenable Terrascan

- [CVE-2026-47357](https://insights.sbomify.com/CVE-2026-47357/): Server-side request forgery in Terrascan (critical 9.3)
- [CVE-2026-47358](https://insights.sbomify.com/CVE-2026-47358/): Server-side request forgery in Terrascan (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47356 and fix it if it is affected.

What it is: CVE-2026-47356 is a high-severity server-side request forgery vulnerability in tenable Terrascan, published on 19 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47356 in the wild and no public exploit code.

Affected product: tenable Terrascan. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47356/ (Markdown: https://insights.sbomify.com/CVE-2026-47356/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47356
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47356
- OSV: https://osv.dev/vulnerability/CVE-2026-47356

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47356/
Summaries are generated and may contain mistakes; the official description above is the record.