VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

ursa: vulnerability history, versions and safety

ursa is a package in the crates.io ecosystem. Vulert records 2 vulnerabilities for it across 21 releases, first recorded in Jan 2024. 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 M2
i
2 with no fix published

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

See the unfixed vulnerabilities →
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 ursa vulnerabilities

Vulert verdict on ursa 0.3.7 i

Updated on 23 Oct 2026

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

Package health score 58/100
  • Security Minor issues
  • Maintenance Slowing
  • 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.3.7 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 16 Jan 2024 i
  • Highest CVSS 6.5 i
  • With no published fix 2 i
  • Depended on by 5 packages i
  • Stars 324 i
  • OpenSSF scorecard 4/10 i
  • Last release 61 months ago i
  • Licence Apache-2.0 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 ursa, 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.3.7 15 Sep 2021 M2 Apache-2.0 No Details →
0.3.6 05 May 2021 M2 Apache-2.0 No Details →
0.3.5 19 Aug 2020 M2 Apache-2.0 No Details →
0.3.4 07 Jul 2020 M2 Apache-2.0 No Details →
0.3.2 10 Feb 2020 M2 Apache-2.0 No Details →
0.3.1 23 Jan 2020 M2 Apache-2.0 No Details →
0.3.0 11 Dec 2019 M2 Apache-2.0 No Details →
0.2.0 02 Oct 2019 M2 Apache-2.0 No Details →
0.2.0-dev-6 02 Oct 2019 M2 Apache-2.0 No Details →
0.2.0-dev-5 02 Oct 2019 M2 Apache-2.0 No Details →
0.2.0-dev-4 02 Oct 2019 M2 Apache-2.0 No Details →
0.2.0-dev-3 02 Oct 2019 M2 Apache-2.0 No Details →
0.2.0-dev-2 01 Oct 2019 M2 Apache-2.0 No Details →
0.2.0-dev-1 26 Aug 2019 M2 Apache-2.0 No Details →
0.1.1 18 Apr 2019 M2 Apache-2.0 No Details →
0.1.1-dev-2 08 Apr 2019 M2 Apache-2.0 No Details →
0.1.1-dev-1 04 Apr 2019 M2 Apache-2.0 No Details →
0.1.0 21 Mar 2019 M2 Apache-2.0 No Details →
0.1.0-dev-3 05 Feb 2019 M2 Apache-2.0 No Details →
0.1.0-dev-2 31 Jan 2019 M2 Apache-2.0 No Details →
0.1.0-dev-1 31 Jan 2019 M2 Apache-2.0 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 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 ursa

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-22192: Ursa CL-Signatures Revocation Allows Verifiers to Generate Unique Identifiers for Holders 6.5 medium No fix published 16 Jan 2024
CVE-2024-21670: Ursa CL-Signatures Revocation Scheme Flaw in Open Source Package 'ursa' 6.5 medium No fix published 16 Jan 2024

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 ursa

Is ursa safe to use?

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

What is ursa's Vulert package health score?

Vulert scores ursa 58/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 ursa affected?

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

Which version of ursa should I use?

0.3.7 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 ursa have?

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

How often are new ursa vulnerabilities disclosed?

0 vulnerabilities were recorded for ursa in the last 12 months, and the oldest entry in this database dates to 16 Jan 2024. 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 ursa 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 ursa for upcoming vulnerabilities?

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