Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0078 json

Symbol confusion after hasher panic in `intaglio` interners

published 7mo ago modified 6mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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.

Patch / fix

  • crates.io intaglio 1.13.3

Is RUSTSEC-2026-0078 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io intaglio
>=0.0.0-0, <1.13.3
1.13.3

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.