Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Resource budgets not enforced on the typed deserialization path

GHSA-4xcc-23fx-w2wj

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (noyalib 0.0.53), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io noyalib

    Affected
    >= 0.0.0-0, < 0.0.53
    Fixed in
    0.0.53

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

`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:: ` 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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record RUSTSEC-2026-0333

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-4xcc-23fx-w2wj

Advisory: Resource budgets not enforced on the typed deserialization path
IDs: GHSA-4xcc-23fx-w2wj
Record: https://patchnext.com/advisories/rustsec-2026-0333 (revision 1, source checked 23 Oct 2026, 22:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: noyalib 0.0.53. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io noyalib: affected >= 0.0.0-0, < 0.0.53; fixed in 0.0.53

## Suggested inspection (read-only)
- crates.io noyalib: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on noyalib.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/RUSTSEC-2026-0333 (OSV record RUSTSEC-2026-0333 lists affected ranges: crates.io noyalib >=0.0.0-0 <0.0.53 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…