# RUSTSEC-2026-0333: Resource budgets not enforced on the typed deserialization path

> Attackers can bypass resource limits in typed deserialization, causing denial of service if custom budgets were configured.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Also known as:** GHSA-4xcc-23fx-w2wj

## What is RUSTSEC-2026-0333?

RUSTSEC-2026-0333 is a denial of service vulnerability in noyalib, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

`ParserConfig::max_events`, `max_nodes`, `max_total_scalar_bytes`,
`max_merge_keys`, `alias_anchor_ratio` and the alias jump factor were
enforced only by the two `Value` loaders. A typed target with a
default-shaped configuration is served by the streaming deserializer,
which never read those fields, so tightening any of them had no effect
on `from_str::<T>` for a struct target. The default document-length,
depth and alias-count caps were enforced on every path, so no input was
unbounded; the gap affects callers who tightened the other budgets for
hostile input.

Version 0.0.53 charges every budget on the streaming path as well and
adds cross-path parity tests.

Users who cannot upgrade can deserialize into `noyalib::Value` first and
convert with `from_value`, or rely on `max_document_length` and
`max_depth`, which were always applied on every path.

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `noyalib` | crates.io | From 0.0.0-0 | 0.0.53 |

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

Upgrade noyalib to 0.0.53 or later.

## Is RUSTSEC-2026-0333 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: RUSTSEC-2026-0333 is a denial of service vulnerability in noyalib, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of RUSTSEC-2026-0333 in the wild and no public exploit code.

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

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

## Sources

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

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