core

Vulnerabilities · Unnamed version

Published by nanobom on vulnerabilities.xila.dev.

Scope and provenance

Software bill of materials
uploaded on 2026-11-20 17:34 UTC
Components checked
314
Components not checked
43 components without a package URL
Last check against OSV
2026-11-20 17:34 UTC
CISA KEV catalog last read
2026-11-19 03:00 UTC
FIRST EPSS scores last read
2026-11-19 03:00 UTC

Summary

No open vulnerabilities of high or critical severity; 12 of lower or unknown severity.

12 open findings

  • 0Critical
  • 0High
  • 0Medium
  • 0Low
  • 12Unknown
  • 0 known exploited
Assessed and ignored
0
Fixed in the last 90 days
5

Open vulnerabilities

Known exploited first, then by severity and EPSS. EPSS is the percentile of the probability of exploitation in the next 30 days.

Open vulnerabilities, known exploited first
VulnerabilityComponentSeverityKnown exploitedEPSSFixed inFirst seen
RUSTSEC-2026-0574`FindMutView::pop` after mutating the value would lead to a use after freeheapless0.9.3pkg:cargo/heapless@0.9.3UnknownNo 0.9.42026-11-19
RUSTSEC-2026-0575`Spsc::peek` used `Relaxed` ordering where it should have use `Acquire`heapless0.9.3pkg:cargo/heapless@0.9.3UnknownNo 0.9.42026-11-19
RUSTSEC-2026-0576`IndexMap::truncate` could lead to an inconsistent stateheapless0.9.3pkg:cargo/heapless@0.9.3UnknownNo 0.9.42026-11-19
RUSTSEC-2026-0577Panicking `Drop` implementation could lead to UBheapless0.9.3pkg:cargo/heapless@0.9.3UnknownNo 0.9.42026-11-19
RUSTSEC-2026-0578`SortedLinkedList::zeroize` lead to an inconsistent stateheapless0.9.3pkg:cargo/heapless@0.9.3UnknownNo 0.9.42026-11-19
RUSTSEC-2026-0579The `Deque` implementation from `TryFrom` was wrong when the `Deque` ended up fullheapless0.9.3pkg:cargo/heapless@0.9.3UnknownNo 0.9.42026-11-19
RUSTSEC-2026-0580The treiber stack implementation in heapless had a race conditionheapless0.9.3pkg:cargo/heapless@0.9.3UnknownNo 0.9.42026-11-19
RUSTSEC-2026-0581`Deque::make_contiguous` could lead to broken invariantsheapless0.9.3pkg:cargo/heapless@0.9.3UnknownNo 0.9.42026-11-19
RUSTSEC-2026-0582On maps of `u16::MAX` elements, `IndexMap::insert` could lead to a broken invariantheapless0.9.3pkg:cargo/heapless@0.9.3UnknownNo 0.9.42026-11-19
RUSTSEC-2024-0384`instant` is unmaintainedinstant0.1.13pkg:cargo/instant@0.1.13UnknownNo Not known2026-11-18
RUSTSEC-2026-0441`pin-utils` is unmaintainedpin-utils0.1.1pkg:cargo/pin-utils@0.1.1UnknownNo Not known2026-11-18
RUSTSEC-2026-0486GHSA-jh2m-fhpj-3vr7xattr functions mark unwritten bytes as initialized when given a zero-length bufferrustix1.1.5pkg:cargo/rustix@1.1.5UnknownNo 1.1.62026-11-18

Assessed by the maintainers

Findings the maintainers assessed and ignored. A justification states why the project is not affected; an ignore without one records an accepted risk.

For scanners, the same assessments as a CycloneDX VEX document: https://vulnerabilities.xila.dev/public/77c21accb207ba9e806b97b994d63a3f/vex.json

No finding was ignored.

Method

nanobom checks the package URL of each component of the SBOM against the OSV vulnerability database, then ranks the findings with the CISA catalog of known exploited vulnerabilities (KEV) and the FIRST exploit prediction scores (EPSS).

It does not check components without a package URL, nor code the SBOM does not list, such as vendored or generated code.

This page shows the state when it was served. Dates are in UTC.