CVE-2026-33875
Gematik Authenticator ≤ 4.16.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:NSummary
CVE-2026-33875 is a critical-severity Improper Verification of Source of a Communication Channel (CWE-940) vulnerability in Gematik Authenticator. Its CVSS base score is 9.3 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique ARP Cache Poisoning (T1557.002); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-17 (Remote Access) and IA-3 (Device Identification and Authentication) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-33875 affects the Gematik Authenticator, a component used to securely authenticate users for login to digital health applications. Versions prior to 4.16.0 are vulnerable to authentication flow hijacking, classified under CWE-940. The issue has a CVSS v3.1 base score of 9.3 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N), indicating high severity due to its network accessibility, low attack complexity, lack of required privileges, reliance on user interaction, expanded scope, and significant impacts on confidentiality and integrity.
Remote attackers with no privileges can exploit this vulnerability by crafting malicious deep links that, when clicked by victims, hijack the authentication flow. This allows attackers to authenticate using the identities of victim users, potentially granting unauthorized access to digital health services tied to the victim's account.
Advisories, including the Gematik GitHub Security Advisory (GHSA-qg87-cf56-2rmr) and the Machine Spirits advisory (https://www.machinespirits.com/advisory/f41e56/), recommend updating the Gematik Authenticator to version 4.16.0 or greater to apply the patch. No workarounds are known.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-16817
Vulnerability Data
Gematik Authenticator securely authenticates users for login to digital health applications. Versions prior to 4.16.0 are vulnerable to authentication flow hijacking, potentially allowing attackers to authenticate with the identities of victim users who click on a malicious deep link. Update…
more
Gematik Authenticator to version 4.16.0 or greater to receive a patch. There are no known workarounds.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.5.3V10.6.2V15.2.4
Mitigating Controls (NIST 800-53 r5) AI
IA-3 requires unique identification and authentication of devices before any communication channel is established, directly stopping acceptance of unverified origins.
AC-17 mandates documented restrictions and authentication requirements for remote access, blocking channels whose origins are not properly verified.
SC-23 protects session authenticity, ensuring the source of an established communication channel is verified and cannot be spoofed.
SC-7 enforces monitoring and control at external and key internal interfaces, preventing channels from unverified sources via boundary rules.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Authentication of users/services/hardware directly enforces source verification for communication channels.
Verifying identity assertions prevents spoofed channel origins but does not cover all channel-establishment scenarios.
Network protections reduce unauthorized channel usage but do not specifically require origin verification at channel setup.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure authentication mechanisms verify the identity and origin of communication channel initiators.
Network security controls enforce source verification and channel authentication for incoming communications.
Security of network services includes validating the origin of service requests and connections.
Network segregation limits exposure but does not directly verify source of individual channels.
Cryptography can support channel authentication but does not inherently verify source without proper implementation.
Application security requirements may specify origin checks but do not mandate them.