How severe is GHSA-pv9v-5j35-xwcr?

No CVSS score has been assigned to GHSA-pv9v-5j35-xwcr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pv9v-5j35-xwcr?

GHSA-pv9v-5j35-xwcr affects the following packages: libcrux-poly1305 (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-pv9v-5j35-xwcr?

Update libcrux-poly1305 to 0.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pv9v-5j35-xwcr is resolved across your whole dependency graph.

How do I detect GHSA-pv9v-5j35-xwcr in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libcrux-poly1305, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-pv9v-5j35-xwcr 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-pv9v-5j35-xwcr?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pv9v-5j35-xwcr can be triaged on real exposure rather than presence alone.

Is GHSA-pv9v-5j35-xwcr actively exploited in the wild?

No public exploit code has been indexed for GHSA-pv9v-5j35-xwcr 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-pv9v-5j35-xwcr published, and has it been updated?

GHSA-pv9v-5j35-xwcr was published on March 26, 2026 and was last updated on March 27, 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

Not in CISA KEV

GHSA-pv9v-5j35-xwcr — libcrux-poly1305

Fix: cryspen/libcrux#1351

GHSA-pv9v-5j35-xwcr is a security vulnerability in libcrux-poly1305. A fix is available for libcrux-poly1305 — see the affected versions and patch details below.

libcrux Panics During Standalone MAC Operations

Also known asRUSTSEC-2026-0073

Published

Mar 26, 2026

Updated

Mar 27, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 27, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀libcrux-poly1305

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

An incorrect constant for the key length in libcrux-poly1305 caused the standalone MAC function libcrux_poly1305::mac to always panic with an out-of-bounds memory access.

Impact

Applications wishing to use libcrux-poly1305 as a standalone MAC would experience panics. The use of libcrux-poly1305 in libcrux-chacha20poly1305 is unaffected.

Mitigation

Starting from version 0.0.5, the correct value is used for the key length constant.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`libcrux-poly1305`	all versions	0.0.5`cargo update -p libcrux-poly1305 --precise 0.0.5`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libcrux-poly1305, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update libcrux-poly1305 to 0.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pv9v-5j35-xwcr 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pv9v-5j35-xwcr can be triaged on real exposure rather than presence alone.

Tailored to GHSA-pv9v-5j35-xwcr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An incorrect constant for the key length in libcrux-poly1305 caused the standalone MAC function `libcrux_poly1305::mac` to always panic with an out-of-bounds memory access. ## Impact Applications wishing to use libcrux-poly1305 as a standalone MAC would experience panics. The use of libcrux-poly1305 in libcrux-chacha20poly1305 is unaffected. ## Mitigation Starting from version `0.0.5`, the correct value is used for the key length constant.

O3 Security · Impact-Aware SCA

Is GHSA-pv9v-5j35-xwcr in your dependencies?

O3 Security finds GHSA-pv9v-5j35-xwcr across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works