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

> Attackers can cause symbol confusion or panics in Rust applications using intaglio if a custom hasher panics during insertion, leading to data corruption or crashes.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Mar 2026

## What is RUSTSEC-2026-0078?

RUSTSEC-2026-0078 is a vulnerability in intaglio, published on 30 Mar 2026. 

### Official description

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.

## Which versions are affected by RUSTSEC-2026-0078?

1 open source package ship an affected version, including intaglio.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `intaglio` | crates.io | From 0.0.0-0 | 1.13.3 |

## How do I fix RUSTSEC-2026-0078?

Upgrade intaglio to 1.13.3 or later.

## Is RUSTSEC-2026-0078 being exploited?

There is no known exploitation of RUSTSEC-2026-0078 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2026-0078 and fix it if it is affected.

What it is: RUSTSEC-2026-0078 is a vulnerability in intaglio, published on 30 Mar 2026. 
Exploitation: There is no known exploitation of RUSTSEC-2026-0078 in the wild and no public exploit code.

Affected packages and fixed versions:
- intaglio (crates.io): affected from 0.0.0-0; fixed in 1.13.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/RUSTSEC-2026-0078/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0078/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2026-0078

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2026-0078/
Summaries are generated and may contain mistakes; the official description above is the record.