RUSTSEC-2026-0078: Symbol confusion after hasher panic in `intaglio` interners

What to do

1. See which version you have: cargo tree -i intaglio (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p intaglio. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example intaglio = "1.13.3") 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

Affected versions of this crate can leave all SymbolTable variants in an internally inconsistent state if a custom BuildHasher panics during HashMap::insert and the caller recovers with catch_unwind.

The intern implementations committed a vec.push(...) before the matching map.insert(...) completed. If hashing panicked in that window, later lookups and inserts could observe diverging vec and map lengths.

In release builds, this can lead to symbol confusion where a newly interned string resolves to previously interned attacker-controlled contents. In debug builds, the same corruption is detected by follow-up assertions and results in panics.

The flaw was corrected in version 1.13.3 by making the vec mutation transactional across unwind boundaries so partially inserted entries are rolled back before the panic propagates.

References

• Package: crates.io/crates/intaglio
• Advisory: rustsec.org/advisories/RUSTSEC-2026-0078.html
• Report: github.com/artichoke/intaglio/issues/359
• Web: github.com/artichoke/intaglio/pull/360

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 intaglio

• UnsoundRUSTSEC-2023-0048 · 2023-07-26Unsoundness in `intern` methods on `intaglio` symbol interners

Full security history of intaglio