# CVE-2026-27945: GO-2026-4574 - ZITADEL has potential SSRF via Actions in github.com/zitadel/zitadel

Source: https://junglewise.ai/threats/cve-2026-27945-zitadel-has-potential-ssrf-via-actions  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-03-10  
License: CC BY 4.0 with a link back

CVE-2026-27945 · Severity: medium · CVSS 4 · Published 2026-03-10

ZITADEL has potential SSRF via Actions in github.com/zitadel/zitadel

Technologies: [github.com/zitadel/zitadel (Go)](https://junglewise.ai/threats/technologies/github-com-zitadel-zitadel), [github.com/zitadel/zitadel/v2 (Go)](https://junglewise.ai/threats/technologies/github-com-zitadel-zitadel-v2). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2026-27945 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-27945 being exploited in the wild.

**How severe is CVE-2026-27945?** Medium severity, with a CVSS score of 4, published 10 March 2026.

**Which products and versions are affected?** github.com/zitadel/zitadel (Go) SEMVER:introduced=0,fixed=1.80.0-v2.20.0.20260225053328-b2532e966621; github.com/zitadel/zitadel/v2 (Go) SEMVER:introduced=2.59.0,fixed=4.11.1.

**Is there a fix for CVE-2026-27945?** Yes. github.com/zitadel/zitadel (Go): upgrade to 1.80.0-v2.20.0.20260225053328-b2532e966621 or later; github.com/zitadel/zitadel/v2 (Go): upgrade to 4.11.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-27945?** Check whether you run github.com/zitadel/zitadel (Go) or github.com/zitadel/zitadel/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/zitadel/zitadel (Go): upgrade to 1.80.0-v2.20.0.20260225053328-b2532e966621 or later

  ```sh
  go get github.com/zitadel/zitadel@v1.80.0-v2.20.0.20260225053328-b2532e966621
  ```

- github.com/zitadel/zitadel/v2 (Go): upgrade to 4.11.1 or later

  ```sh
  go get github.com/zitadel/zitadel/v2@v4.11.1
  ```


## Affected products

- github.com/zitadel/zitadel (Go) SEMVER:introduced=0,fixed=1.80.0-v2.20.0.20260225053328-b2532e966621
- github.com/zitadel/zitadel/v2 (Go) SEMVER:introduced=2.59.0,fixed=4.11.1

## Identifiers

- CVE-2026-27945
- GHSA-7777-fhq9-592v
- GO-2026-4574

## Related threats

- [ZITADEL Actions V1 sandbox escape via require() filesystem read](https://junglewise.ai/threats/cve-2026-85057-zitadel-actions-v1-sandbox-escape-via-require-filesystem-read)
- [ZITADEL Login V2 MFA bypass via session reuse](https://junglewise.ai/threats/cve-2026-85056-zitadel-login-v2-mfa-bypass-via-session-reuse)
- [ZITADEL improper role revocation on granted projects](https://junglewise.ai/threats/cve-2026-76081-zitadel-improper-role-revocation-on-granted-projects)
- [ZITADEL incorrect authorization in email and phone self-management API](https://junglewise.ai/threats/cve-2026-54693-zitadel-incorrect-authorization-in-email-and-phone-self)
- [ZITADEL privilege escalation in OAuth2 Token Exchange](https://junglewise.ai/threats/cve-2026-56668-zitadel-privilege-escalation-in-oauth2-token-exchange)