CVE-2026-27023
Undergoing Analysis Undergoing Analysis - In Progress
SSRF via Unvalidated Redirects in Twenty CRM SecureHttpClientService

Publication date: 2026-03-05

Last updated on: 2026-03-10

Assigner: GitHub, Inc.

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-05
Last Modified
2026-03-10
Generated
2026-05-07
AI Q&A
2026-03-05
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
twenty twenty to 1.18.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

[{'type': 'paragraph', 'content': 'CVE-2026-27023 is a Server-Side Request Forgery (SSRF) vulnerability in the SecureHttpClientService of the open source CRM called Twenty, affecting versions prior to 1.18.'}, {'type': 'paragraph', 'content': 'The vulnerability occurs because the SSRF protection only validated the IP address of the initial request URL but did not validate the IP addresses of HTTP redirect targets. This means that an authenticated user who can control outbound request URLs (like webhook endpoints or image URLs) could bypass private IP blocking by redirecting requests through an attacker-controlled server.'}, {'type': 'paragraph', 'content': "Additionally, the HTTP adapter used automatically follows redirects without revalidating the redirected URLs' IPs, and cross-protocol redirects (e.g., HTTPS to HTTP) bypassed certain security agents, further enabling the bypass."}, {'type': 'paragraph', 'content': 'This issue was patched in version 1.18 by moving IP validation from the request level to the connection level, ensuring every TCP connection, including those from redirects, is validated.'}] [2]


How can this vulnerability impact me? :

An authenticated attacker with low privileges and no user interaction required can exploit this vulnerability to bypass private IP blocking and access internal network resources.

This can allow the attacker to read internal network responses, potentially exposing confidential data such as sensitive cloud metadata endpoints.

The vulnerability has a moderate severity with a CVSS v3.1 base score of 5.0, indicating a significant risk of confidentiality impact.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability involves SSRF attacks exploiting redirect targets that bypass IP validation. Detection would involve monitoring outbound HTTP requests, especially those that follow redirects, and inspecting if any requests are redirected to private or sensitive IP addresses such as internal network ranges or cloud metadata endpoints (e.g., 169.254.169.254).

Since the vulnerability is related to authenticated users controlling outbound request URLs (like webhook endpoints or image URLs), reviewing logs for unusual or unexpected outbound requests and redirects can help detect exploitation attempts.

Specific commands are not provided in the resources, but general network monitoring commands could include:

  • Using tcpdump or Wireshark to capture and analyze outbound HTTP traffic and redirects.
  • Using curl with verbose output to manually test webhook or image URLs for unexpected redirects, e.g., `curl -v <URL>`.
  • Checking application logs for outbound HTTP requests and their redirect chains.

What immediate steps should I take to mitigate this vulnerability?

[{'type': 'paragraph', 'content': 'The primary mitigation is to upgrade the twenty CRM software to version 1.18 or later, where the vulnerability has been patched.'}, {'type': 'paragraph', 'content': 'The patch moves IP validation from the request level to the connection level, ensuring that every TCP connection, including those from redirects, is validated to prevent SSRF bypass.'}, {'type': 'paragraph', 'content': "Until the upgrade is applied, restrict authenticated users' ability to control outbound request URLs, such as webhook endpoints or image URLs, to trusted domains only."}, {'type': 'paragraph', 'content': 'Additionally, monitor and restrict outbound HTTP redirects and implement network-level controls to block unauthorized access to private IP ranges and sensitive endpoints.'}] [2, 1]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart