cargo package report

Is salsa 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-xc3w-55vh-cw3w, the advisory selected below

      // 1 advisories

      GHSA-xc3w-55vh-cw3w

      UNKNOWN

      When an application reads an interned value's fields or uses that value as an input to a tracked function, Salsa must ensure that reusable storage has been validated for the current database revision. This prevents the value's fields and associated cached function results from being freed while in use. Affected versions checked this invariant only with debugassert! when reading fields, and did not check it when using an interned value to access a tracked function's cached result.

      Bugs in Salsa's dependency tracking, or an application-provided Eq implementation that incorrectly treats a changed query result as unchanged, can cause Salsa to reuse cached results containing stale interned values. If the application accesses these values and then interns additional values, Salsa can free the old fields or cached function results while references to them are still in use. This causes use-after-free through safe Rust APIs. Depending on the consuming application, attacker-controlled input may expose process memory or permit arbitrary code execution.

      The fix asserts that an interned value's reusable storage has been validated for the current database revision before allowing an application to read its fields or access a tracked function's cached result using that value as input. If the assertion fails, Salsa panics before returning references to storage that could be freed while in use.

      Salsa 0.28.5 and newer address this vulnerability. Dependent applications should update Salsa and rebuild.

      Applications that disable garbage collection for all explicitly declared interned structs using #[salsa::interned(revisions = usize::MAX)] and do not use implicitly interned query arguments are not affected by this vulnerability.

      Checked 2026-09-25 at 16:43 UTC. The most recent advisory here was published 2026-09-24. Updated continuously from NVD, GHSA, OSV and CNA feeds.

      Think a verdict here is wrong? Tell us — we respond within 2 business days.
      Is salsa safe? cargo package security report | CyberXYZ