VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

redox_uefi_std: vulnerability history, versions and safety

redox_uefi_std is a package in the crates.io ecosystem. Vulert records 2 vulnerabilities for it across 6 releases, from Mar 2025 to May 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded L1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all redox_uefi_std vulnerabilities

Vulert verdict on redox_uefi_std 0.1.14 i

Updated on 23 Oct 2026

Good news: 0.1.14, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 73/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Not enough data

What to do: Stay on 0.1.14 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.1.14 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.1.14 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 06 May 2025 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 17 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by crates.io, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for redox_uefi_std, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.1.14 02 May 2025 none MIT — Details →
0.1.13 16 Oct 2024 L1 U1 MIT Yes Details →
0.1.12 17 May 2024 L1 U1 MIT Yes Details →
0.1.11 22 Mar 2024 L1 U1 MIT Yes Details →
0.1.10 11 Feb 2023 L1 U1 MIT Yes Details →
0.1.9 19 Nov 2022 L1 U1 MIT Yes Details →
0.1.8 21 Oct 2022 L1 U1 MIT Yes Details →
0.1.7 01 Apr 2022 none MIT — Details →
0.1.6 02 Mar 2022 none MIT — Details →
0.1.5 19 Oct 2021 none MIT — Details →
0.1.4 17 Dec 2020 none MIT — Details →
0.1.3 07 Oct 2020 none MIT — Details →
0.1.2 04 Nov 2019 none MIT — Details →
0.1.1 08 Oct 2019 none MIT — Details →
0.1.0 15 Mar 2019 none MIT — Details →

All 15 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for redox_uefi_std

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap Buffer Overflow Vulnerability in Redox UEFI Safe API N/A low 0.1.14 06 May 2025
Heap Buffer Overflow Vulnerability in redox_uefi_std Package N/A unrated 0.1.14 27 Mar 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About redox_uefi_std

Is redox_uefi_std safe to use?

Vulert records 2 vulnerabilities for redox_uefi_std in crates.io: 0 critical, 0 high, 0 medium and 1 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is redox_uefi_std's Vulert package health score?

Vulert scores redox_uefi_std 73/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of redox_uefi_std affected?

No. 0.1.14, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of redox_uefi_std should I use?

0.1.14 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does redox_uefi_std have?

2 vulnerabilities are recorded for redox_uefi_std in the crates.io ecosystem: 0 critical, 0 high, 0 medium and 1 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new redox_uefi_std vulnerabilities disclosed?

0 vulnerabilities were recorded for redox_uefi_std in the last 12 months, and the oldest entry in this database dates to 27 Mar 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of redox_uefi_std are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor redox_uefi_std for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the redox_uefi_std version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.