CVE-2026-74875
openssl_encrypt <1.4.0 skips JSON schema validation if jsonschema missing, accepting malformed metadata.
Is CVE-2026-74875 being exploited?
Not confirmed. CVE-2026-74875 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.18% probability of exploitation in the next 30 days.
How severe is CVE-2026-74875?
CVE-2026-74875 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-74875?
Yes. A fix has been recorded for CVE-2026-74875. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74875 affect?
CVE-2026-74875 affects openssl_encrypt < 1.4.0, Python applications using openssl_encrypt without jsonschema, Systems processing metadata via this library. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74875?
Upgrade to openssl_encrypt >=1.4.0, ensure jsonschema is installed, and audit metadata handling.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Validation bypass lets attackers supply/process malicious metadata, enabling data corruption, injection, or unsafe parsing in affected apps.
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.