# CVE-2026-27023: Twenty: SSRF protection bypass via HTTP redirect following in secure HTTP client

> Authenticated attackers can bypass SSRF protections in Twenty CRM by exploiting unvalidated HTTP redirects, potentially accessing internal network resources.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A: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:** 5 Mar 2026
- **Updated:** 6 Mar 2026
- **Also known as:** GHSA-wm7q-rvq3-x8q9

## What is CVE-2026-27023?

CVE-2026-27023 is a medium-severity server-side request forgery vulnerability in twentyhq twenty, published on 5 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Twenty is an open source CRM. Prior to version 1.18, the SSRF protection in SecureHttpClientService validated request URLs at the request level but did not validate redirect targets. An authenticated user who could control outbound request URLs (e.g., webhook endpoints, image URLs) could bypass private IP blocking by redirecting through an attacker-controlled server. This issue has been patched in version 1.18.

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

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

It affects 1 product.


Products: Twenty Twenty.

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

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

## Is CVE-2026-27023 being exploited?

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

## Other vulnerabilities in twentyhq twenty

- [CVE-2026-46624](https://insights.sbomify.com/CVE-2026-46624/): Twenty: SQL Injection via the timeZone field (critical 9.9)
- [CVE-2026-26720](https://insights.sbomify.com/CVE-2026-26720/): Code injection in n/a (critical 9.8)
- [CVE-2026-44729](https://insights.sbomify.com/CVE-2026-44729/): Twenty: Stored Cross-Site Scripting via Unsanitized File Serving (Missing Content-Type/Content-Disposition Headers) (high 8.7)
- [CVE-2024-28434](https://insights.sbomify.com/CVE-2024-28434/): Cross-site scripting in n/a (high 7.6)
- [CVE-2024-28435](https://insights.sbomify.com/CVE-2024-28435/): Server-side request forgery in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27023 is a medium-severity server-side request forgery vulnerability in twentyhq twenty, published on 5 Mar 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-27023 in the wild and no public exploit code.

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

## Sources

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

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