CVE-2026-105211

waiting for further signalsZero needs more public information before it can validate it.

GHSA-mq63-7hcv-jfrc ↗EUVD-2026-92104 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
zitadel < 4.17.1
fixed in 4.17.1
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
ETK-2026-564, permanent identifier
14d 15h 18msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+52h28m
0
+2h
+4h
+6h
+8h
+10h

description

ZITADEL Login V2 versions before 4.17.1 can permit unauthenticated account takeover. An attacker needs the login name of a target account configured with email and SMS one-time-password factors; privileged accounts may also be affected.

mitigation

Upgrade ZITADEL to version 4.17.1 or later. Prioritize systems using Login V2 and accounts configured with both email and SMS OTP factors.

fixed in 4.17.1

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.33%25th percentile
agent run time
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-04 13:10Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-04 13:10Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-105211

{
  "etk_id": "ETK-2026-564",
  "cve_id": "CVE-2026-105211",
  "display_id": "CVE-2026-105211",
  "ghsa_id": "GHSA-mq63-7hcv-jfrc",
  "euvd_id": "EUVD-2026-92104",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in ZITADEL Login V2",
  "summary": "ZITADEL Login V2 versions before 4.17.1 can permit unauthenticated account takeover. An attacker needs the login name of a target account configured with email and SMS one-time-password factors; privileged accounts may also be affected.",
  "mitigation": "Upgrade ZITADEL to version 4.17.1 or later. Prioritize systems using Login V2 and accounts configured with both email and SMS OTP factors.",
  "vendor": "zitadel",
  "product": "zitadel",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 4.17.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "4.17.1"
      ],
      "package_name": "zitadel",
      "purl": null
    }
  ],
  "cwes": [
    200
  ],
  "cvss_score": 9.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0033,
  "epss_percentile": 0.2507,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 18.321074883333335,
  "t0_at": "2026-10-04T13:10:04.626000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-04T13:10:04.626000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-04T13:10:04.626000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-105211"
    }
  }
}

published 2026-10-04 15:20Z
last change 2026-10-21 08:40Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.