Skip to content
Applications

CVE-2026-74885

9.3
Critical
EPSS 0.12%Patch availableAug 17, 2026

Library logging bug corrupts audit trails; race condition can bypass module hiding.

common questions

Is CVE-2026-74885 being exploited?

Not confirmed. CVE-2026-74885 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.12% probability of exploitation in the next 30 days.

How severe is CVE-2026-74885?

CVE-2026-74885 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-74885?

Yes. A fix has been recorded for CVE-2026-74885. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-74885 affect?

CVE-2026-74885 affects openssl_encrypt < 1.4.0, Apps using restore_hidden_modules() module-hiding, Multi-threaded apps with import hooks. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74885?

Upgrade to 1.4.0+ or apply vendor patch; audit logs and test module-hiding in multithreaded environments.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
openssl_encrypt < 1.4.0Apps using restore_hidden_modules() module-hidingMulti-threaded apps with import hooks
impact

Corrupts audit logs and may allow re-import/execution of previously blocked modules in multithreaded apps, enabling policy bypass or unauthorized code execution.

action required

Immediate action required

affected versions
jahlives openssl_encrypt
  • affected< 1.4.0
vendor says fixed in1.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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free