# CVE-2026-73082: Activepieces: Server-side request forgery in MCP tool validation endpoint

> An authenticated user can trigger server-side requests to internal or external hosts via the MCP tool validation endpoint, potentially exposing internal network details.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-7qx9-q4xx-rh59

## What is CVE-2026-73082?

CVE-2026-73082 is a medium-severity server-side request forgery vulnerability in activepieces, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Activepieces is an open source AI workflow automation platform. Prior to 0.82.0, the POST /api/v1/projects/:projectId/mcp-server/validate-agent-mcp-tool endpoint makes an outbound HTTP or SSE request to a user-supplied serverUrl without URL validation or SSRF protection. An authenticated user can cause the Activepieces server to connect to internal services, cloud metadata endpoints, or arbitrary external hosts and probe network reachability from the Activepieces host. This issue is fixed in version 0.82.0.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-73082 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73082 is a medium-severity server-side request forgery vulnerability in activepieces, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-73082 in the wild and no public exploit code.

Affected product: activepieces. 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-73082/ (Markdown: https://insights.sbomify.com/CVE-2026-73082/index.md)
```

## Sources

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

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