CVE-2026-33874
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. Starting in version 4.12.0 and prior to version 4.16.0, the Mac OS version of the Authenticator is vulnerable to remote code execution, triggered when victims open a malicious file. Update the 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 confidenceThe Gematik Authenticator application for Mac OS (versions 4.12.0 through before 4.16.0) contains a remote code execution vulnerability that triggers when a user opens a malicious file, allowing attackers to execute arbitrary code on the affected system.
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.12.0, < 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 the /Applications folder for the Gematik Authenticator.app application bundle, or search using Spotlight (Cmd+F in Finder, search for 'Gematik Authenticator')Affected if The application exists on the system
-
Locate the installed version numberRight-click Gematik Authenticator.app in Applications, select 'Get Info', and read the version number under the 'General' information section. Alternatively, run this command in Terminal: defaults read /Applications/Gematik\ Authenticator.app/Contents/Info.plist CFBundleShortVersionStringAffected if A version number is returned from the application
-
Compare version against affected rangeTake the installed version and determine whether it falls within >= 4.12.0 and < 4.16.0Affected if The installed version is 4.12.0, 4.12.1, 4.13.0, 4.14.0, 4.15.0, 4.15.1, or any version starting with 4.12 through 4.15 (but not 4.16.0 or higher)
The system is affected if Gematik Authenticator is installed and its version is 4.12.0 or higher but lower than 4.16.0.
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 the Gematik Authenticator to version 4.16.0 or later on all affected Mac OS systems to remediate this file-based RCE vulnerability.
version 4.16.0 or greater
- Download Gematik Authenticator version 4.16.0 or later from the official vendor source
- Install the updated version, replacing the vulnerable installation (versions 4.12.0 through 4.15.x)
- Verify the installed version is 4.16.0 or greater after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33874 — 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-33874 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