How severe is GHSA-8c75-8mhr-p7r9?

No CVSS score has been assigned to GHSA-8c75-8mhr-p7r9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8c75-8mhr-p7r9?

GHSA-8c75-8mhr-p7r9 affects the following packages: openssl (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-8c75-8mhr-p7r9?

Update openssl to 0.10.78 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8c75-8mhr-p7r9 is resolved across your whole dependency graph.

How do I detect GHSA-8c75-8mhr-p7r9 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-8c75-8mhr-p7r9 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-8c75-8mhr-p7r9?

O3 pinpoints whether GHSA-8c75-8mhr-p7r9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-8c75-8mhr-p7r9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-8c75-8mhr-p7r9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-8c75-8mhr-p7r9 published, and has it been updated?

GHSA-8c75-8mhr-p7r9 was published on April 22, 2026 and was last updated on May 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

GHSA-8c75-8mhr-p7r9

Fix: rust-openssl/rust-openssl#2604

GHSA-8c75-8mhr-p7r9 is a security vulnerability in openssl. O3 Security confirms whether GHSA-8c75-8mhr-p7r9 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

rust-openssl has incorrect bounds assertion in aes key wrap

Also known asCVE-2026-41678

Published

Apr 22, 2026

Updated

May 5, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

🦀openssl

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Summary

aes::unwrap_key() has an incorrect bounds assertion on the out buffer size, which can lead to out-of-bounds write.

Details

aes::unwrap_key() contains an incorrect assertion: it checks that out.len() + 8 <= in_.len(), but this condition is reversed. The intended invariant is out.len() >= in_.len() - 8, ensuring the output buffer is large enough.

Because of the inverted check, the function only accepts buffers at or below the minimum required size and rejects larger ones. If a smaller buffer is provided the function will write past the end of out by in_.len() - 8 - out.len() bytes, causing an out-of-bounds write from a safe public function.

Impact

Vulnerable applications using AES keywrap and allowing attacker controlled buffer sizes could have an attacker trigger an out-of-bounds write.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`openssl`	≥ 0.10.24&&< 0.10.78	0.10.78

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openssl to 0.10.78 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8c75-8mhr-p7r9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-8c75-8mhr-p7r9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-8c75-8mhr-p7r9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary ``aes::unwrap_key()`` has an incorrect bounds assertion on the out buffer size, which can lead to out-of-bounds write. ### Details ``aes::unwrap_key()`` contains an incorrect assertion: it checks that `out.len() + 8 <= in_.len()`, but this condition is reversed. The intended invariant is `out.len() >= in_.len() - 8`, ensuring the output buffer is large enough. Because of the inverted check, the function only accepts buffers at or below the minimum required size and rejects larger ones. If a smaller buffer is provided the function will write past the end of `out` by `in_.len() - 8

O3 Security · Impact-Aware SCA

Is GHSA-8c75-8mhr-p7r9 in your dependencies?

O3 detects GHSA-8c75-8mhr-p7r9 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works