Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9

ZITADEL has improper HTML sanitization in emails and Console UI

CVE-2024-41953GHSA-v333-7h2p-5fhv

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/zitadel/zitadel 2.58.1, 2.57.1, 2.56.2, 2.55.5, 2.54.8, 2.53.9, 2.52.3, 1.80.0-v2.20.0.20240731122110-189505c80fa6, 0.0.0-20240731122110-189505c80fa6), 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.

Add to your agent

Affected packages

  • Go github.com/zitadel/zitadel

    Affected
    >= 2.53.0, < 2.53.9>= 2.54.0, < 2.54.8>= 2.55.0, < 2.55.5>= 2.56.0, < 2.56.2>= 2.57.0, <= 2.57.0>= 2.58.0, <= 2.58.0< 0.0.0-20240731122110-189505c80fa6>= 1.80.1, < 2.52.3< 1.80.0-v2.20.0.20240731122110-189505c80fa6
    Fixed in
    2.55.5, 2.52.3, 2.56.2, 2.57.1, 0.0.0-20240731122110-189505c80fa6, 2.54.8, 2.58.1, 2.53.9, 1.80.0-v2.20.0.20240731122110-189505c80fa6

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-v333-7h2p-5fhv lists affected ranges: Go github.com/zitadel/zitadel >=2.53.0 =2.54.0 =2.55.0 =2.56.0 =2.57.0 =2.58.0 =0 =1.80.1 =0.0.0 <1.80.0-v2.20.0.20240731122110-189505c80fa6

    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 4.0
6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2024-41953: 0.65% estimated exploitation activity in the next 30 days; percentile 51.23 (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.

Impact ZITADEL uses HTML for emails and renders certain information such as usernames dynamically. That information can be entered by users or administrators. Due to a missing output sanitization, these emails could include malicious code. This may potentially lead to a threat where an attacker, without privileges, could send out altered notifications that are part of the registration processes. An attacker could create a malicious link, where the injected code would be rendered as part of the email. During investigation of this issue a related issue was found and mitigated, where on the user's detail page the username was not sanitized and would also render HTML, giving an attacker the same vulnerability. While it was possible to inject HTML including javascript, the execution of such scripts would be prevented by most email clients and the Content Security Policy in Console UI. Patches 2.x versions are fixed on = 2.58.1 2.57.x versions are fixed on = 2.57.1 2.56.x versions are…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-v333-7h2p-5fhv

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-41953

Advisory: ZITADEL has improper HTML sanitization in emails and Console UI
IDs: CVE-2024-41953, GHSA-v333-7h2p-5fhv
Record: https://patchnext.com/advisories/cve-2024-41953 (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 6.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.58.1, 2.57.1, 2.56.2, 2.55.5, 2.54.8, 2.53.9, 2.52.3, 1.80.0-v2.20.0.20240731122110-189505c80fa6, 0.0.0-20240731122110-189505c80fa6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/zitadel/zitadel: affected >= 2.53.0, < 2.53.9; >= 2.54.0, < 2.54.8; >= 2.55.0, < 2.55.5; >= 2.56.0, < 2.56.2; >= 2.57.0, <= 2.57.0; >= 2.58.0, <= 2.58.0; < 0.0.0-20240731122110-189505c80fa6; >= 1.80.1, < 2.52.3; < 1.80.0-v2.20.0.20240731122110-189505c80fa6; fixed in 2.55.5, 2.52.3, 2.56.2, 2.57.1, 0.0.0-20240731122110-189505c80fa6, 2.54.8, 2.58.1, 2.53.9, 1.80.0-v2.20.0.20240731122110-189505c80fa6

## 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-v333-7h2p-5fhv (GitHub-reviewed advisory GHSA-v333-7h2p-5fhv lists affected ranges: Go github.com/zitadel/zitadel >=2.53.0 =2.54.0 =2.55.0 =2.56.0 =2.57.0 =2.58.0 =0 =1.80.1 =0.0.0 <1.80.0-v2.20.0.20240731122110-189505c80fa6)

Commands are suggestions: review each one before running it.

Loading voting…