Denied Host Validation Bypass in Zitadel Actions
CVE-2024-49753GHSA-6cf5-w9h3-4rqv
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/zitadel/zitadel 2.64.1, 2.63.6, 2.62.8, 2.61.4, 2.60.4, 2.59.5, 2.58.7, 1.80.0-v2.20.0.20241022141644-79fb4cc1cc6e, 0.0.0-20241022141644-79fb4cc1cc6e), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- >= 2.64.0, <= 2.64.0>= 2.63.0, < 2.63.6>= 2.62.0, < 2.62.8>= 2.61.0, < 2.61.4>= 2.60.0, < 2.60.4>= 2.59.0, < 2.59.5< 0.0.0-20241022141644-79fb4cc1cc6e>= 1.80.1, < 2.58.7< 1.80.0-v2.20.0.20241022141644-79fb4cc1cc6e
- Fixed in
- 2.60.4, 0.0.0-20241022141644-79fb4cc1cc6e, 1.80.0-v2.20.0.20241022141644-79fb4cc1cc6e, 2.64.1, 2.62.8, 2.58.7, 2.59.5, 2.63.6, 2.61.4
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-6cf5-w9h3-4rqv lists affected ranges: Go github.com/zitadel/zitadel >=2.64.0 =2.63.0 =2.62.0 =2.61.0 =2.60.0 =2.59.0 =0 =1.80.1 =0.0.0 <1.80.0-v2.20.0.20241022141644-79fb4cc1cc6e
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.9 · CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
- EPSS
- CVE-2024-49753: 0.65% estimated exploitation activity in the next 30 days; percentile 51.31 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary A flaw in the URL validation mechanism of Zitadel actions allows bypassing restrictions intended to block requests to localhost (127.0.0.1). The isHostBlocked check, designed to prevent such requests, can be circumvented by creating a DNS record that resolves to 127.0.0.1. This enables actions to send requests to localhost despite the intended security measures. Details While attempting to send a request directly to 127.0.0.1 via an action results in an error (see image below), the restriction can be bypassed using a custom DNS record. <img width="781" alt="image" src="https://github.com/user-attachments/assets/6d22dae8-407f-4420-a937-aca53d22d05d" The relevant action code demonstrates the attempted request to 127.0.0.1: By creating a DNS record that resolves a custom domain to 127.0.0.1 (illustrated below using messwithdns), the action can successfully send the request. The modified action code uses the custom domain instead of 127.0.0.1: This demonstrates that data from the…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-6cf5-w9h3-4rqv
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2024-49753 Advisory: Denied Host Validation Bypass in Zitadel Actions IDs: CVE-2024-49753, GHSA-6cf5-w9h3-4rqv Record: https://patchnext.com/advisories/cve-2024-49753 (revision 1, source checked 26 Oct 2026, 15:09 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.9) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/zitadel/zitadel 2.64.1, 2.63.6, 2.62.8, 2.61.4, 2.60.4, 2.59.5, 2.58.7, 1.80.0-v2.20.0.20241022141644-79fb4cc1cc6e, 0.0.0-20241022141644-79fb4cc1cc6e. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/zitadel/zitadel: affected >= 2.64.0, <= 2.64.0; >= 2.63.0, < 2.63.6; >= 2.62.0, < 2.62.8; >= 2.61.0, < 2.61.4; >= 2.60.0, < 2.60.4; >= 2.59.0, < 2.59.5; < 0.0.0-20241022141644-79fb4cc1cc6e; >= 1.80.1, < 2.58.7; < 1.80.0-v2.20.0.20241022141644-79fb4cc1cc6e; fixed in 2.60.4, 0.0.0-20241022141644-79fb4cc1cc6e, 1.80.0-v2.20.0.20241022141644-79fb4cc1cc6e, 2.64.1, 2.62.8, 2.58.7, 2.59.5, 2.63.6, 2.61.4 ## Suggested inspection (read-only) - Go github.com/zitadel/zitadel: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/zitadel/zitadel. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-6cf5-w9h3-4rqv (GitHub-reviewed advisory GHSA-6cf5-w9h3-4rqv lists affected ranges: Go github.com/zitadel/zitadel >=2.64.0 =2.63.0 =2.62.0 =2.61.0 =2.60.0 =2.59.0 =0 =1.80.1 =0.0.0 <1.80.0-v2.20.0.20241022141644-79fb4cc1cc6e) Commands are suggestions: review each one before running it.
Loading voting…