CVE-2026-33875
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGematik 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 Gematik Authenticator to version 4.16.0 or greater to receive a patch. There are no known workarounds.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGematik Authenticator versions prior to 4.16.0 contain an authentication flow hijacking vulnerability where victims clicking malicious deep links may have their authentication session intercepted, allowing attackers to authenticate with victim user identities.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.16.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Gematik Authenticator is installedCheck for Gematik Authenticator application on the system (typical locations: Windows Programs menu, macOS Applications folder, or mobile device app list)Affected if The application is present on the system
-
Determine the installed versionOpen Gematik Authenticator and navigate to the About or Settings section to view the version number, or check the application's properties/details in the system control panelAffected if Unable to determine the version or version displayed is below 4.16.0
-
Compare version against affected rangeCompare the identified version number to the vulnerable range: any version prior to 4.16.0 is affectedAffected if Installed version is less than 4.16.0 (for example, 4.15.2, 4.14.0, etc.)
-
Assess deep link exposureDetermine if the application is configured to handle deep links or has been used for authentication flows, as this is the attack vector for session hijackingAffected if Deep link handling is enabled and the application has been used for authentication sessions
User is affected if Gematik Authenticator version is installed and the version is below 4.16.0, and the application handles authentication via deep links.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.16.0
Update Gematik Authenticator to version 4.16.0 or greater to apply the vendor patch; no workarounds are available.
Gematik Authenticator 4.16.0 or later
- 1. Verify current Gematik Authenticator version by checking the application settings or about menu
- 2. Download Gematik Authenticator version 4.16.0 or later from the official vendor source
- 3. Back up any existing configuration data if required by the application
- 4. Install the updated Gematik Authenticator version 4.16.0
- 5. After installation, verify the version number reflects the update
- 6. Test authentication flows to confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33875 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33875 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data