VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

rsa: vulnerability history, versions and safety

rsa is a package in the crates.io ecosystem. Vulert records 4 vulnerabilities for it across 65 releases, from Nov 2023 to Jan 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded M2 L1 U1
i
3 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 06 Jan 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all rsa vulnerabilities

Vulert verdict on rsa 0.9.10 i

Updated on 23 Oct 2026

Careful: 0.9.10 has 3 known vulnerabilities, and 3 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.9.10 — affected i
  • Vulnerabilities on record 4 over 2 years · 1 in the last year i
  • Latest disclosure 06 Jan 2026 i
  • Highest CVSS 5.9 i
  • With no published fix 3 i
  • Stars 672 i
  • OpenSSF scorecard 4/10 i
  • Last release 9 months ago i
  • Licence Apache-2.0 OR MIT i

Version list, release dates, licence and dependants published by crates.io, refreshed 22 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 rsa, 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.10.0-rc.19 06 Oct 2026 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.18 27 Apr 2026 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.17 10 Mar 2026 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.16 27 Feb 2026 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.15 03 Feb 2026 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.14 25 Jan 2026 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.13 21 Jan 2026 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.12 12 Jan 2026 M2 U1 Apache-2.0 OR MIT No Details →
0.9.10 06 Jan 2026 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.11 03 Jan 2026 M2 U1 Apache-2.0 OR MIT No Details →
0.9.9 13 Nov 2025 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.10 07 Nov 2025 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.9 30 Sep 2025 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.8 14 Sep 2025 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.7 14 Sep 2025 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.6 03 Sep 2025 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.5 26 Aug 2025 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.4 06 Aug 2025 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.3 10 Jul 2025 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.2 10 Jul 2025 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.1 21 Jun 2025 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-rc.0 31 May 2025 M2 U1 Apache-2.0 OR MIT No Details →
0.9.8 12 Mar 2025 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.10.0-pre.4 14 Feb 2025 M2 U1 Apache-2.0 OR MIT No Details →
0.9.7 26 Nov 2024 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.10.0-pre.3 08 Oct 2024 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-pre.2 28 Jul 2024 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-pre.1 06 Feb 2024 M2 U1 Apache-2.0 OR MIT No Details →
0.10.0-pre.0 19 Jan 2024 M2 U1 Apache-2.0 OR MIT No Details →
0.9.6 01 Dec 2023 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.9.5 28 Nov 2023 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.9.4 20 Nov 2023 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.9.3 26 Oct 2023 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.9.2 08 May 2023 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.9.1 04 May 2023 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.9.0 27 Apr 2023 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.9.0-rc.0 25 Apr 2023 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.9.0-pre.2 19 Apr 2023 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.9.0-pre.1 05 Apr 2023 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.9.0-pre.0 06 Mar 2023 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.8.2 02 Mar 2023 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.8.1 21 Jan 2023 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.8.0 17 Jan 2023 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.8.0-rc.0 11 Jan 2023 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.8.0-pre.0 17 Dec 2022 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.7.2 15 Nov 2022 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.7.1 31 Oct 2022 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.7.0 10 Oct 2022 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.7.0-rc.1 05 Oct 2022 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.7.0-rc.0 16 Sep 2022 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.7.0-pre 24 May 2022 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.6.1 11 Apr 2022 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.6.0 08 Apr 2022 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.6.0-pre 10 Mar 2022 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.5.0 27 Jul 2021 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.4.1 26 Jul 2021 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.4.0 28 Mar 2021 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.3.0 11 Jun 2020 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.2.0 11 Dec 2019 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.1.4 13 Oct 2019 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.1.3 26 Mar 2019 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.1.2 25 Feb 2019 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.1.1 20 Feb 2019 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.1.0 05 Dec 2018 M2 L1 U1 Apache-2.0 OR MIT No Details →
0.0.0 24 Jul 2018 M2 L1 Apache-2.0 OR MIT No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 3
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for rsa

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Marvin Attack: Potential Key Recovery Through Timing Sidechannels in Rust rsa 5.9 medium No fix published 22 Nov 2023
Marvin Attack: RSA Vulnerability in Rust rsa crate 5.9 medium No fix published 28 Nov 2023
CVE-2023-49092: Timing Sidechannel Attack in RSA Package 5.9 medium No fix published 28 Nov 2023
Panic Risk in RSA Crate: Handling Prime Value of 1 2.7 low 0.9.10 06 Jan 2026

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 rsa

Is rsa safe to use?

Vulert records 4 vulnerabilities for rsa in crates.io: 0 critical, 0 high, 2 medium and 1 low, plus 1 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is rsa's Vulert package health score?

Vulert scores rsa 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of rsa affected?

Yes. 0.9.10, the version you would install today, has 3 known vulnerabilities, and 3 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of rsa should I use?

0.9.10 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 rsa have?

4 vulnerabilities are recorded for rsa in the crates.io ecosystem: 0 critical, 0 high, 2 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 rsa vulnerabilities disclosed?

1 vulnerability was recorded for rsa in the last 12 months, and the oldest entry in this database dates to 22 Nov 2023. 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 rsa 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 rsa for upcoming vulnerabilities?

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