External risk intelligence

Gematik Authenticator Authentication Flow Hijacking

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-33875

The Gematik Authenticator is a client-side application used for identity verification. The vulnerability requires a user to click a malicious deep link, which is a client-side interaction rather than an internet-facing service, gateway, or network-accessible endpoint that could be scanned or reached directly from the public internet.

Gematik Authenticator

before 4.16.0

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory highlights a security flaw in the Gematik Authenticator, a tool used for securely logging into digital health applications. The vulnerability could allow attackers to impersonate legitimate users if they trick them into clicking a malicious link, potentially compromising user identities within these health platforms.

  • Authentication hijacking in health app login.
  • Protects user identities in digital health services.
  • Confirm relevance; risk mitigation is key.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into clicking a malicious link, which would then redirect them to a compromised application. This could lead to the attacker hijacking the user's authentication flow and gaining access to their digital health applications with the victim's identity.

  • Requires user to click a malicious link.
  • Hijacks the authentication flow.
  • Attacker impersonates victim users.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an attacker to hijack the authentication flow for digital health applications. When supported, a victim user clicking a malicious deep link may result in an attacker authenticating as that user.

  • User identities and application access at risk.
  • Victims clicking malicious deep links.
  • Unauthorized access to health application data.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Gematik Authenticator, used for digital health application logins, requires action from teams managing user identity and digital health platforms. The immediate priority is to locate all instances of the affected Authenticator, confirm their reachability and criticality to business operations, and identify the responsible application or platform owner to initiate a risk-based remediation plan.

  • Identify owners of affected Authenticator.
  • Verify user impact and reachability.
  • Plan and execute updates based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Gematik Authenticator?

The Gematik Authenticator is a client-side application designed to provide secure identity verification. Users rely on this software to authenticate their identity when accessing various digital health applications, ensuring that only authorized individuals can interact with sensitive health data.

How does CVE-2026-33875 affect the login process?

This vulnerability is classified as improper verification of authentication data, or CWE-940. It allows an attacker to manipulate the authentication flow. By exploiting how the software handles specific links, an unauthorized party can trick the system into authenticating them as a different, legitimate user.

Does just having the app installed trigger the vulnerability?

No. The flaw is not triggered by simply having the software installed or running. It specifically requires a user interaction where they must click on a malicious deep link. If a user does not interact with such a deceptive link, this specific path to hijacking remains inactive.

Is this vulnerability reachable from the internet?

Halo Surface Signal indicates it is very unlikely to be reachable from the internet because the Authenticator is a client-side tool. Since it is not an internet-facing service or server endpoint, an attacker cannot scan for or directly exploit it remotely without the user's manual interaction.

What should I do to address this risk?

The necessary response is to update the Gematik Authenticator to version 4.16.0 or higher. There are no available workarounds, so prioritizing the deployment of this update is the only effective way to remediate the vulnerability and protect the authentication flow of your digital health applications.

References