CVE-2026-74876
Library flaw lets attacker-crafted public keys encrypt and leak secrets.
Is CVE-2026-74876 being exploited?
Not confirmed. CVE-2026-74876 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.20% probability of exploitation in the next 30 days.
How severe is CVE-2026-74876?
CVE-2026-74876 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-74876?
Yes. A fix has been recorded for CVE-2026-74876. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74876 affect?
CVE-2026-74876 affects openssl_encrypt < 1.4.0, Any app using PublicKeyBundle.from_dict(), Services performing client-side/public-key encryption. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74876?
Upgrade to openssl_encrypt >=1.4.0, validate signatures, rotate affected keys
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can create key bundles via from_dict() to encrypt data with attacker-controlled public keys, causing secret disclosure and impersonation.
Immediate action required
- affected< 1.4.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.