{"answers":{"affected":"1 open source package ship an affected version, including noyalib.","exploited":"There is no known exploitation of RUSTSEC-2026-0333 in the wild and no public exploit code.","fix":"Upgrade noyalib to 0.0.53 or later.","what":"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."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0333 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of RUSTSEC-2026-0333 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- noyalib (crates.io): affected from 0.0.0-0; fixed in 0.0.53\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/RUSTSEC-2026-0333/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0333/index.md)","id":"RUSTSEC-2026-0333","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0333/index.md","name":"RUSTSEC-2026-0333","record":{"aliases":["GHSA-4xcc-23fx-w2wj"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Rust YAML parser","requires_auth":"none","summary":"Attackers can bypass resource limits in typed deserialization, causing denial of service if custom budgets were configured.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"`ParserConfig::max_events`, `max_nodes`, `max_total_scalar_bytes`,\n`max_merge_keys`, `alias_anchor_ratio` and the alias jump factor were\nenforced only by the two `Value` loaders. A typed target with a\ndefault-shaped configuration is served by the streaming deserializer,\nwhich never read those fields, so tightening any of them had no effect\non `from_str::\u003cT\u003e` for a struct target. The default document-length,\ndepth and alias-count caps were enforced on every path, so no input was\nunbounded; the gap affects callers who tightened the other budgets for\nhostile input.\n\nVersion 0.0.53 charges every budget on the streaming path as well and\nadds cross-path parity tests.\n\nUsers who cannot upgrade can deserialize into `noyalib::Value` first and\nconvert with `from_value`, or rely on `max_document_length` and\n`max_depth`, which were always applied on every path.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Resource budgets not enforced on the typed deserialization path","id":"RUSTSEC-2026-0333","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.0.53"],"introduced":["0.0.0-0"],"last_affected":[],"package":"noyalib","purl":"pkg:cargo/noyalib","source":"RUSTSEC-2026-0333"}],"products":null,"published":"2026-10-06","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can bypass resource limits in typed deserialization, causing denial of service if custom budgets were configured.","url":"https://insights.sbomify.com/RUSTSEC-2026-0333/"}