cargo package report

Is noyalib safe?

1 known vulnerability.

// reach

0 direct dependencies

none carry a known advisory

    0 packages depend on it

    an advisory here reaches each of them

      Create a free accountfor every dependency path, dependent and what to upgrade
      // ai model usage

      Tracked for PyPI packages. HuggingFace models declare Python dependencies, so cargo packages are not covered.

      cvss
      not scored

      severity out of 10

      epss
      not scored

      chance of exploitation in 30 days

      xyz score
      not scored

      CyberXYZ composite out of 10

      fig. 01 — GHSA-4xcc-23fx-w2wj, the advisory selected below

      // 1 advisories

      GHSA-4xcc-23fx-w2wj

      UNKNOWN

      ParserConfig::maxevents, maxnodes, maxtotalscalarbytes, maxmergekeys, aliasanchorratio 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 fromstr:: 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 fromvalue, or rely on maxdocumentlength and maxdepth, which were always applied on every path.

      Checked 2026-10-09 at 23:56 UTC. The most recent advisory here was published 2026-10-06. Updated continuously from NVD, GHSA, OSV and CNA feeds.

      Think a verdict here is wrong? Tell us — we respond within 2 business days.