Inventory exposes reference to non-Sync data to an arbitrary thread
Priority LOW 38Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
Affected versions do not enforce a `Sync` bound on the type of caller-provided value held in the plugin registry. References to these values are made accessible to arbitrary threads other than the one that constructed them. A caller could use this flaw to submit thread-unsafe data into inventory, then access it as a reference simultaneously from multiple threads. The flaw was corrected by enforcing that data submitted by the caller into inventory is `Sync`.
Why it matters now
Fix Fixed inventory (crates.io): 0.2.0
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | inventory (crates.io) | before 0.2.0 | 0.2.0 | Patch available | GHSA-36xm-35qq-795w |
- inventory (crates.io) Vendor— Affected before 0.2.0 Fixed in 0.2.0 Patch available GHSA-36xm-35qq-795w
Remediation
- Fix · GHSA-36xm-35qq-795w inventory (crates.io) Fixed in 0.2.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-36xm-35qq-795w
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences