dbcve.org
Rust OpensslFramework / library · Rust Openssl Project

CVE-2026-41898

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-24
Fix available
A fix is available. Upgrade to 0.10.78 or later.
See remediation →
62/100
Remediation priority · Elevated
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.9.24 to before 0.10.78, the FFI trampolines behind SslContextBuilder::set_psk_client_callback, set_psk_server_callback, set_cookie_generate_cb, and set_stateless_cookie_generate_cb forwarded the user closure's returned usize directly to OpenSSL without checking it against the &mut [u8] that was handed to the closure. This can lead to buffer overflows and other unintended consequences. 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 versions 0.9.24 through 0.10.77 have a buffer overflow vulnerability in FFI trampolines for PSK and cookie callback functions. The callbacks return a usize value directly to OpenSSL without validating it against the provided buffer size (&mut [u8]), allowing attackers to overflow the buffer.

MitigationUpgrade rust-openssl to version 0.10.78 or later to receive the bounds-checking fix.

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.9.24, < 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
Low
Integrity
None
Availability
None

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

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. Check rust-openssl version in Cargo.lock
    Search for 'name = "openssl"' in Cargo.lock and read the version field beside it
    Affected if Version is 0.9.24 through 0.10.77 (any version >= 0.9.24 and < 0.10.78)
  2. Check Cargo.toml for rust-openssl dependency
    Look for openssl under [dependencies] or [dev-dependencies] and note the version range specified
    Affected if The version constraint allows versions 0.9.24 through 0.10.77 (for example, ">= 0.9.24" or any "0.10" version before 0.10.78)
  3. Search for PSK client callback usage
    Grep or search the codebase for 'set_psk_client_callback' string
    Affected if This function is called in the code
  4. Search for PSK server callback usage
    Grep or search the codebase for 'set_psk_server_callback' string
    Affected if This function is called in the code
  5. Search for cookie generation callback usage
    Grep or search the codebase for 'set_cookie_generate_cb' and 'set_stateless_cookie_generate_cb' strings
    Affected if Either of these functions is called in the code

You are affected if your rust-openssl version is 0.9.24 through 0.10.77 AND your code uses any of the PSK or cookie generation callback functions (set_psk_client_callback, set_psk_server_callback, set_cookie_generate_cb, or set_stateless_cookie_generate_cb).

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 receive the bounds-checking fix.

Recommended fix High confidence

0.10.78

  1. Update the rust-openssl dependency in Cargo.toml to version 0.10.78 or later: change `openssl = "0.9.x"` to `openssl = "0.10.78"` or use a compatible semver range like `openssl = ">=0.9.24,<0.10.78"` is vulnerable; use `openssl = ">=0.10.78"`
  2. Run `cargo update` to fetch the fixed version
  3. Run `cargo build` to rebuild with the patched OpenSSL bindings
  4. Test the application thoroughly, especially any code using set_psk_client_callback, set_psk_server_callback, set_cookie_generate_cb, or set_stateless_cookie_generate_cb to ensure PSK and cookie functionality still works correctly
Caveat Review the rust-openssl changelog between your current version and 0.10.78 for any API changes to PSK or cookie callback methods

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

Fix this in Rust Openssl Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41898 — 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-41898 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