CVE-2026-41681
DigestFinal overflow in rust-openssl can corrupt stack.
Is CVE-2026-41681 being exploited?
Not confirmed. CVE-2026-41681 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.36% probability of exploitation in the next 30 days.
How severe is CVE-2026-41681?
CVE-2026-41681 is rated High with a CVSS score of 8.1. 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-41681?
Yes. A fix has been recorded for CVE-2026-41681. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-41681 affect?
CVE-2026-41681 affects rust-openssl crate versions 0.10.39 - 0.10.77, Rust/OpenSSL usage in affected apps. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41681?
Upgrade to 0.10.78 or newer
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Stack corruption via digest_final; could crash process or enable exploit.
Patch when possible
- affected>= 0.10.39 and < 0.10.78
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.