dbcve.org
Rust OpensslFramework / library · Rust Openssl Project

CVE-2026-41681

HIGH · 7.5 CVSS v3.1 Published 2026-04-24
Fix available
A fix is available. Upgrade to 0.10.78 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
rust-openssl provides OpenSSL bindings for the Rust programming language. From 0.10.39 to before 0.10.78, EVP_DigestFinal() always writes EVP_MD_CTX_size(ctx) to the out buffer. If out is smaller than that, MdCtxRef::digest_final() writes past its end, usually corrupting the stack. This is reachable from safe Rust. This vulnerability is fixed in 0.10.78.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The rust-openssl library contains a buffer overflow vulnerability in MdCtxRef::digest_final() where EVP_DigestFinal() writes EVP_MD_CTX_size(ctx) bytes to the output buffer without validating buffer size. When the out buffer is smaller than required, writes extend past the buffer boundary, corrupting the stack. This is exploitable from safe Rust code.

MitigationUpgrade rust-openssl to version 0.10.78 or later to resolve the unbounded buffer write in digest_final().

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Rust OpensslFramework / library
Affected:>= 0.10.39, < 0.10.78

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate rust-openssl dependency
    Inspect your Cargo.toml file and look for the openssl crate entry in the [dependencies] section, or check Cargo.lock for the openssl package entry
    Affected if rust-openssl is present as a dependency
  2. Determine installed rust-openssl version
    Check the version number specified next to the openssl crate in Cargo.lock, or run `cargo tree -p openssl` to see the exact version being used
    Affected if The version is >= 0.10.39 and < 0.10.78 (or if you cannot determine the version and the crate is present)
  3. Find digest_final() usage in source code
    Search your codebase for calls to MdCtxRef::digest_final or digest_final using grep or your IDE's search functionality
    Affected if Code calls digest_final() on an MdCtxRef instance
  4. Inspect buffer sizing in digest_final calls
    Review each digest_final() call to see what buffer is passed as the output parameter and whether it is sized to hold at least EVP_MD_CTX_size(ctx) bytes (typically 32 bytes for SHA-256, 64 for SHA-512, etc.)
    Affected if The output buffer passed to digest_final() is smaller than the expected hash size for the algorithm being used

You are affected if your project uses rust-openssl version 0.10.39 through 0.10.77 and contains code that calls MdCtxRef::digest_final() with an undersized output buffer.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.10.78 or later
Fixed in 0.10.78
Vendor patch github.com →
Interim mitigation

Upgrade rust-openssl to version 0.10.78 or later to resolve the unbounded buffer write in digest_final().

Recommended fix High confidence

0.10.78

  1. Update the Cargo.toml dependency to specify version 0.10.78: openssl = "0.10.78"
  2. Run `cargo update` or `cargo build` to fetch and compile the fixed version
  3. Verify the installed version by checking Cargo.lock or running `cargo tree | grep openssl`

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rust Openssl Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41681 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41681 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data