Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
RUSTSEC-2026-0337
Poly1305 in ic-cipher absorbs messages of 64 bytes or more four blocks at
a time, summing four products before one reduction. From 0.2.5 to 0.2.19 the
reduction kept its carries in 32-bit integers, which four summed products can
overflow when the message's bytes are large.
This affects Poly1305 and ChaCha20Poly1305, and everything built on them:
the TLS and QUIC ChaCha20-Poly1305 suites in ic-rustls, HPKE with that
cipher in ic-hpke, and the re-exports in ic-mac and ironcrypto.
What happens depends on how the crate was compiled:
- With overflow checks on (any debug build, or a release profile with
overflow-checks = true) the multiplication panics, and underpanic = "abort"the process ends. The tag is computed over the ciphertext before it is compared, so this happens before authentication and without the key: anyone who can deliver a ChaCha20-Poly1305 ciphertext to be opened can trigger it. - With overflow checks off (Cargo's default for release builds) the arithmetic wraps and the tag is computed wrong on the affected messages.
Ordinary data does not reach the defect. A message of 0xff bytes does: in
one measurement against 0.2.19, 28 of 500 ChaCha20Poly1305::open_detached
calls on 1,024 bytes of 0xff under random keys and nonces panicked in a
debug build. ChaCha20-Poly1305 derives a new Poly1305 key for every nonce, so
each message is a fresh attempt.
AES-GCM and AES-GCM-SIV are not affected, and neither are messages shorter than 64 bytes.
The flaw was corrected in 0.2.20 by carrying in 64 bits.
It was found by running Project Wycheproof's ChaCha20-Poly1305 test vectors against the library.
Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.
Drag and drop some file here, or click to select
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the availability of the system.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
Probability that this vulnerability will be exploited in the wild within the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard