# Resource budgets not enforced on the typed deserialization path Advisory record · `GHSA-4xcc-23fx-w2wj` - **Identifiers:** `GHSA-4xcc-23fx-w2wj` · `RUSTSEC-2026-0333` - **State:** Confirmed - **Severity:** No CVSS score - **Critical:** No - **Published:** 6 Oct 2026 - **Updated:** 8 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 6 Oct 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `noyalib` (crates.io): affected `>=0.0.0-0, <0.0.53`; fixed in `0.0.53` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Versions of noyalib before 0.0.53 do not enforce several resource budgets (max_events, max_nodes, max_total_scalar_bytes, max_merge_keys, alias_anchor_ratio and the alias jump factor) when deserializing into a typed struct with from_str. The default document-length, depth and alias-count limits still apply, so input was not unbounded, but callers who tightened these budgets for untrusted input were not protected. Upgrade to noyalib 0.0.53, which applies all budgets on this path; until then, deserialize into noyalib::Value and convert with from_value, which enforces them. Written 3 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation No source has published a CVSS score for this record yet. - **CISA KEV:** Not listed. - **EPSS:** No score. ## Timeline - 31 Oct 2026, 14:24 UTC: First seen by agentprime - 31 Oct 2026, 14:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/RUSTSEC-2026-0333) ## Sources - [GitHub Advisory Database: GHSA-4xcc-23fx-w2wj](https://github.com/advisories/GHSA-4xcc-23fx-w2wj) - [OSV: GHSA-4xcc-23fx-w2wj](https://osv.dev/vulnerability/GHSA-4xcc-23fx-w2wj) - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .