Security readout for executives and security teams
Plain-English summary
ZITADEL could let users mark their own email address or phone number as verified without completing verification. If your business relies on ZITADEL’s “verified” status for account trust, onboarding, recovery, or authorization decisions, this can weaken identity assurance.
Executive priority
Treat as high priority if ZITADEL verified contact status is used for security or business decisions. Patch promptly and review affected identity workflows for improper trust decisions.
Technical view
CVE-2026-27946 is a CWE-862 missing authorization issue in ZITADEL self-management. Before fixed versions 4.11.1 and 3.4.7, the UpdateHumanUser API could accept verification flags from users without requiring the correct permission, allowing self-verification of email or phone values.
Likely exposure
Exposure is likely for ZITADEL deployments running affected versions and allowing user self-management where verified email or phone status affects trust, workflows, access, or fraud controls.
Exploitation context
The public sources do not report active exploitation, and the CVE is not listed as KEV. Exploitation requires interaction with ZITADEL’s user self-management capability, not compromise of the underlying host.
Researcher notes
The advisory identifies missing authorization around verification flags in UpdateHumanUser. Sources name fixed versions and a workaround, but do not provide evidence of exploitation in the wild. Avoid assuming broader account takeover without environment-specific trust dependencies.
Mitigation direction
- Upgrade ZITADEL to version 4.11.1 or 3.4.7 as applicable.
- If upgrade is not possible, use an action v2 to block setting own verification flags.
- Review vendor advisory for deployment-specific guidance before changing identity workflows.
Validation and detection
- Inventory all ZITADEL instances and record exact versions.
- Confirm whether user self-management is enabled.
- Check whether verified email or phone influences access, onboarding, or recovery.
- Audit recent user profile changes involving verified email or phone flags.
- Verify patched behavior prevents self-setting verification flags without permission.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-27946 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.2 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
8.2HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/zitadel/zitadel/security/advisories/GHSA-282g-fhmx-xf54CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.