{"items":[{"id":"NVI-00015234","kind":"vulnerability","title":"ZITADEL Users Can Self-Verify Email/Phone via API","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jq8w-8q2f-ffm9","CVE-2026-54693"],"plain_summary":"GitHub lists this reviewed advisory for github.com/zitadel/zitadel, github.com/zitadel/zitadel, github.com/zitadel/zitadel. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-467616792d31d45a66f7187e8f279ad0"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-467616792d31d45a66f7187e8f279ad0","url":"https://github.com/advisories/GHSA-jq8w-8q2f-ffm9","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-jq8w-8q2f-ffm9","publisher":"GitHub Advisory Database","observed_at":"2026-11-03T09:58:49.818Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-467616792d31d45a66f7187e8f279ad0"],"technology":"github.com/zitadel/zitadel","known_exclusions":[],"conditions_summary":"### Summary\n\nA vulnerability in Zitadel's self-management capability allowed users to mark their email and phone as verified without going through an actual verification process.\n\nWhile `GHSA-282g-fhmx-xf54` (CVE-2026-27946, \"Users Can Self-Verify Email/Phone via UpdateHumanUser API\") closed the path that let any authenticated user mark an arbitrary email or phone as verified on their own account by calling `UpdateHumanUser` with `email.is_verified: true`, additional paths were discovered.\n\n### Impact \n\nZitadel provides an API for managing users. The API also allows users to self-manage their own data including updating the email and phone.\n\nDue to an improper permission check, the API allowed returning the verification code for the email and phone to the own user.\nThis allows users to claim ownership of an email or phone they do not control and potentially bypass email-based security policies.\n\nNote that when changing another user's email or phone, regardless of the verification flag, the permissions were correctly checked.\n\n### Affected Versions\n\nSystems running one of the following versions are affecte","public_affected_ranges":[">= 4.0.0, < 4.15.1"]},{"certainty":"source_listed","source_ids":["sr-467616792d31d45a66f7187e8f279ad0"],"technology":"github.com/zitadel/zitadel","known_exclusions":[],"conditions_summary":"### Summary\n\nA vulnerability in Zitadel's self-management capability allowed users to mark their email and phone as verified without going through an actual verification process.\n\nWhile `GHSA-282g-fhmx-xf54` (CVE-2026-27946, \"Users Can Self-Verify Email/Phone via UpdateHumanUser API\") closed the path that let any authenticated user mark an arbitrary email or phone as verified on their own account by calling `UpdateHumanUser` with `email.is_verified: true`, additional paths were discovered.\n\n### Impact \n\nZitadel provides an API for managing users. The API also allows users to self-manage their own data including updating the email and phone.\n\nDue to an improper permission check, the API allowed returning the verification code for the email and phone to the own user.\nThis allows users to claim ownership of an email or phone they do not control and potentially bypass email-based security policies.\n\nNote that when changing another user's email or phone, regardless of the verification flag, the permissions were correctly checked.\n\n### Affected Versions\n\nSystems running one of the following versions are affecte","public_affected_ranges":[">= 2.43.0, < 3.4.11"]},{"certainty":"source_listed","source_ids":["sr-467616792d31d45a66f7187e8f279ad0"],"technology":"github.com/zitadel/zitadel","known_exclusions":[],"conditions_summary":"### Summary\n\nA vulnerability in Zitadel's self-management capability allowed users to mark their email and phone as verified without going through an actual verification process.\n\nWhile `GHSA-282g-fhmx-xf54` (CVE-2026-27946, \"Users Can Self-Verify Email/Phone via UpdateHumanUser API\") closed the path that let any authenticated user mark an arbitrary email or phone as verified on their own account by calling `UpdateHumanUser` with `email.is_verified: true`, additional paths were discovered.\n\n### Impact \n\nZitadel provides an API for managing users. The API also allows users to self-manage their own data including updating the email and phone.\n\nDue to an improper permission check, the API allowed returning the verification code for the email and phone to the own user.\nThis allows users to claim ownership of an email or phone they do not control and potentially bypass email-based security policies.\n\nNote that when changing another user's email or phone, regardless of the verification flag, the permissions were correctly checked.\n\n### Affected Versions\n\nSystems running one of the following versions are affecte","public_affected_ranges":["< 1.80.0-v2.20.0.20260608144108-ed09b3df7f43"]}],"null_published_at":"2026-11-03T10:03:26.563Z","source_updated_at":"2026-07-29T16:54:53.000Z","source_disclosed_at":"2026-07-29T16:54:49.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-03T09:58:49.818Z"}],"next_cursor":null,"snapshot_revision":"42594"}