Skip to main content
Mallory
HighVulnerability

CVE-2026-41681: Stack Buffer Overflow in rust-openssl MdCtxRef::digest_final

Published Apr 24, 2026 · Updated 7 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS8.1High · v4
EPSS0.36%30th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
OpenSSL Software Foundation
IdentifiersCVE-2026-41681CWE-121 · Stack-based Buffer Overflow

CVE-2026-41681 is a buffer-overflow vulnerability in the Rust openssl crate, affecting versions 0.10.39 through versions before 0.10.78. MdCtxRef::digest_final() passes a caller-provided output slice to OpenSSL's EVP_DigestFinal() without validating its length. Because EVP_DigestFinal() writes the full digest of EVP_MD_CTX_size(ctx) bytes, an undersized output slice causes an out-of-bounds write, typically corrupting the stack. The vulnerability is reachable through safe Rust code. Version 0.10.78 introduces a length check and returns an error for undersized output slices.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Digest finalization can overwrite memory beyond the caller's output buffer, typically causing stack corruption. This can crash the application or corrupt application state. Depending on application reachability and memory layout, the corruption could potentially enable arbitrary code execution; a working code-execution exploit is not established.

Mitigation

If you can’t patch tonight, do this now.

Until an update can be deployed, ensure every call to MdCtxRef::digest_final() receives an output slice at least as large as the active digest's EVP_MD_CTX_size(ctx) value. Reject undersized slices before invoking the function. No vendor workaround is available for the affected Platform Automation Toolkit release.

Remediation

Patch, then assume compromise.

Upgrade the Rust openssl crate to version 0.10.78 or later and rebuild and redeploy dependent applications. For affected VMware Tanzu Platform Automation Toolkit deployments, upgrade to version 5.5.1. For affected openSUSE 16 installations, apply the security updates for sdbootutil and related packages.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OpenSSL Software FoundationRust-Opensslapplication
FAQ

Frequently asked questions

Is CVE-2026-41681 exploited in the wild?
As of Nov 10, 2026, Mallory has no reports of CVE-2026-41681 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-41681?
As of Nov 10, 2026, Mallory has found no public exploit for CVE-2026-41681.
Is there a patch for CVE-2026-41681?
Upgrade the Rust openssl crate to version 0.10.78 or later and rebuild and redeploy dependent applications. For affected VMware Tanzu Platform Automation Toolkit deployments, upgrade to version 5.5.1.
What products are affected by CVE-2026-41681?
OpenSSL Software Foundation Rust-Openssl.
How severe is CVE-2026-41681?
CVE-2026-41681 has a CVSS v4 score of 8.1 (High) and an EPSS score of 0.36% (30th percentile) as of Nov 10, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.