RUSTSEC-2025-0009: Some AES functions may panic when overflow checking is enabled.

What to do

1. See which version you have: cargo tree -i ring (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p ring. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example ring = "0.17.12") or update the dependency that pulls it in.
3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

ring::aead::quic::HeaderProtectionKey::new_mask() may panic when overflow checking is enabled. In the QUIC protocol, an attacker can induce this panic by sending a specially-crafted packet. Even unintentionally it is likely to occur in 1 out of every 2**32 packets sent and/or received.

On 64-bit targets operations using ring::aead::{AES_128_GCM, AES_256_GCM} may panic when overflow checking is enabled, when encrypting/decrypting approximately 68,719,476,700 bytes (about 64 gigabytes) of data in a single chunk. Protocols like TLS and SSH are not affected by this because those protocols break large amounts of data into small chunks. Similarly, most applications will not attempt to encrypt/decrypt 64GB of data in one chunk.

Overflow checking is not enabled in release mode by default, but RUSTFLAGS="-C overflow-checks" or overflow-checks = true in the Cargo.toml profile can override this. Overflow checking is usually enabled by default in debug mode.

References

• Package: crates.io/crates/ring
• Advisory: rustsec.org/advisories/RUSTSEC-2025-0009.html
• Web: github.com/briansmith/ring/blob/main/RELEASES.md#version-01712-2025-03-05

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.

Other advisories for ring

• UnmaintainedRUSTSEC-2025-0010 · 2025-03-05Versions of *ring* prior to 0.17 are unmaintained.

Full security history of ring