CVE-2026-24736
Published: 27 January 2026
Summary
CVE-2026-24736 is a critical-severity SSRF (CWE-918) vulnerability in Squidex.Io Squidex. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 33.6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified are NIST 800-53 AC-4 (Information Flow Enforcement) and SI-10 (Information Input Validation).
Deeper analysis
CVE-2026-24736 is a server-side request forgery (SSRF) vulnerability, classified under CWE-918, affecting Squidex, an open source headless content management system and content management hub. Versions up to and including 7.21.0 are vulnerable due to inadequate validation of the URL parameter in webhook configurations within the Rules engine. This parameter accepts local addresses such as 127.0.0.1 or localhost without restricting destination IP addresses.
High-privileged users (PR:H per CVSS 3.1 score of 9.1, AV:N/AC:L/UI:N/S:C/C:H/I:H/A:H) can exploit this by defining a webhook with a local or internal URL. When the rule triggers—through manual endpoint calls, content updates, or other events—the backend server issues an HTTP request to the supplied URL and logs the full HTTP response in the rule execution log's lastDump field, which is accessible via the API. This transforms a blind SSRF into a full read SSRF, enabling attackers to retrieve responses from internal services.
The GitHub security advisory (GHSA-wxg2-953m-fg2w) provides further details, but as of the CVE publication on 2026-01-27T21:16:02.967, no patched versions are available. Security practitioners should monitor for updates and consider restricting webhook configurations or rule triggers in affected deployments.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-4742
Vulnerability details
Squidex is an open source headless content management system and content management hub. Versions of the application up to and including 7.21.0 allow users to define "Webhooks" as actions within the Rules engine. The url parameter in the webhook configuration…
more
does not appear to validate or restrict destination IP addresses. It accepts local addresses such as 127.0.0.1 or localhost. When a rule is triggered (Either manual trigger by manually calling the trigger endpoint or by a content update or any other triggers), the backend server executes an HTTP request to the user-supplied URL. Crucially, the server logs the full HTTP response in the rule execution log (lastDump field), which is accessible via the API. Which turns a "Blind" SSRF into a "Full Read" SSRF. As of time of publication, no patched versions are available.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
SSRF in public-facing app directly enables internal/local HTTP requests + response retrieval (T1005 Data from Local System, T1046 Network Service Discovery, T1082 System Information Discovery) and constitutes exploitation of a public-facing application (T1190).
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Directly requires validation of user-supplied webhook URL parameters to reject local or internal addresses, preventing SSRF exploitation.
Enforces approved information flows to block backend HTTP requests to unauthorized internal or local destinations specified in webhook configurations.
Monitors and controls communications at internal interfaces to limit SSRF requests from the backend to internal services and detect anomalous traffic.