# RUSTSEC-2026-0083: zantetsu-trainer is unmaintained


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Apr 2026

## What is RUSTSEC-2026-0083?

RUSTSEC-2026-0083 is a vulnerability in zantetsu-trainer, published on 7 Apr 2026. 

### Official description

The `zantetsu-trainer` crate is no longer maintained. The ML training
infrastructure it contained was removed as part of the zantetsu 0.2 release,
which replaced the neural parser with a pure heuristic engine.

A tombstone version (0.2.0) has been published and 0.1.4 has been yanked.
There is no replacement for `zantetsu-trainer`.

## Migration

If you were using `zantetsu-trainer` as part of a zantetsu-based filename
parsing pipeline, switch to [`zantetsu 0.2`](https://crates.io/crates/zantetsu),
which requires no training step.

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

1 open source package ship an affected version, including zantetsu-trainer.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zantetsu-trainer` | crates.io | From 0.0.0-0 | None |

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

No fix has been published for RUSTSEC-2026-0083 yet. Limit exposure of the affected software until one is available.

## Is RUSTSEC-2026-0083 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: RUSTSEC-2026-0083 is a vulnerability in zantetsu-trainer, published on 7 Apr 2026. 
Exploitation: There is no known exploitation of RUSTSEC-2026-0083 in the wild and no public exploit code.

Affected packages and fixed versions:
- zantetsu-trainer (crates.io): affected from 0.0.0-0; no fix listed

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-0083/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0083/index.md)
```

## Sources

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

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