How severe is CVE-2026-105208?

CVE-2026-105208 has a CVSS 3.x base score of 7.7, rated high severity. It is exploitable over network with high attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2026-105208 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-105208?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-105208 published?

CVE-2026-105208 was published on 2026-10-04 and last updated on 2026-10-05.

CVE-2026-105208

CVE-2026-105208 is a high-severity vulnerability with a CVSS 3.x base score of 7.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-649.

Key facts

Severity: High (CVSS 3.x base score 7.7)
CVSS v4: 8.7
EPSS exploit prediction: 0% (1st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-649
Published: 2026-10-04
Last modified: 2026-10-05

Description

ZITADEL 4.x before 4.17.3 and 3.x through 3.4.15 protects IdP intent tokens with unauthenticated, malleable encryption, allowing authenticated users to tamper with their own token so it is accepted for another user's external login intent. An attacker who predicts a victim's in-flight intent identifier and wins a timing race can call /v2/idp_intents or /v2/sessions to steal the victim's IdP tokens or hijack their session.

Frequently asked questions

What is CVE-2026-105208?: ZITADEL 4.x before 4.17.3 and 3.x through 3.4.15 protects IdP intent tokens with unauthenticated, malleable encryption, allowing authenticated users to tamper with their own token so it is accepted for another user's external login intent. An attacker who predicts a victim's in-flight intent identifier and wins a timing race can call /v2/idp_intents or /v2/sessions to steal the victim's IdP tokens or hijack their session.
How severe is CVE-2026-105208?: CVE-2026-105208 has a CVSS 3.x base score of 7.7, rated high severity. It is exploitable over network with high attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2026-105208 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-105208?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-105208 published?: CVE-2026-105208 was published on 2026-10-04 and last updated on 2026-10-05.

References

Other CWE-649 vulnerabilities

CVE-2024-10772 — High (CVSS 8.8): Since the firmware update is not validated, an attacker can install modified firmware on the device. This has a high…
CVE-2026-95105 — High (CVSS 8.2): Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking vulnerability in…
CVE-2025-41351 — Medium (CVSS 6.0): Vulnerability that allows a Padding Oracle Attack to be performed on the Funambol v30.0.0.20 cloud server. The…
CVE-2010-3300 — Medium (CVSS 5.9): It was found that all OWASP ESAPI for Java up to version 2.0 RC2 are vulnerable to padding oracle attacks.
CVE-2024-36279 — Medium (CVSS 5.3): Reliance on obfuscation or encryption of security-relevant inputs without integrity checking issue exists in "FreeFrom…

Browse all CWE-649 vulnerabilities →