VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

phonenumber: vulnerability history, versions and safety

phonenumber is a package in the crates.io ecosystem. Vulert records 4 vulnerabilities for it across 8 releases, from Sep 2023 to Jul 2024. 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 C1 H1 U2
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 phonenumber vulnerabilities

Vulert verdict on phonenumber 0.3.10+9.0.33 i

Updated on 23 Oct 2026

Good news: 0.3.10+9.0.33, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 75/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release 0.3.10+9.0.33 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 09 Jul 2024 i
  • Highest CVSS 8.6 i
  • With no published fix 0 i
  • Stars 203 i
  • Last release 3 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 phonenumber, 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.10+9.0.33 02 Jul 2026 none Apache-2.0 — Details →
0.3.9+9.0.21 14 Jan 2026 none Apache-2.0 — Details →
0.3.7+8.13.52 11 Jan 2025 none Apache-2.0 — Details →
0.3.6+8.13.36 09 Jul 2024 none Apache-2.0 — Details →
0.3.5+8.13.36 13 May 2024 C1 U1 Apache-2.0 Yes Details →
0.3.4+8.13.34 11 Apr 2024 C1 U1 Apache-2.0 Yes Details →
0.3.3+8.13.9 19 Sep 2023 U1 Apache-2.0 Yes Details →
0.2.5+8.11.3 19 Sep 2023 none Apache-2.0 — Details →
0.3.2+8.13.9 31 Mar 2023 none Apache-2.0 — Details →
0.3.1+8.12.9 12 Oct 2020 none Apache-2.0 — Details →
0.3.0+8.12.9 09 Sep 2020 none Apache-2.0 — Details →
0.2.4+8.11.3 07 Feb 2020 H1 U1 Apache-2.0 Yes Details →
0.2.3+8.10.6 06 Mar 2019 H1 U1 Apache-2.0 Yes Details →
0.2.1+8.9.0 02 Jul 2018 H1 U1 Apache-2.0 Yes Details →
0.2.0+8.9.0 05 Mar 2018 H1 U1 Apache-2.0 Yes Details →
0.1.0+8.7.0 31 Jul 2017 H1 U1 Apache-2.0 Yes Details →

All 16 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 2
  • 2024 2

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

03 Vulnerabilities

Recorded vulnerabilities for phonenumber

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-42444: phonenumber - Panic on Parsing Crafted RF3966 Phonenumber Inputs 8.6 high 0.2.5 19 Sep 2023
CVE-2024-39697: phonenumber - Panic on Parsing Crafted Phonenumber Inputs 8.6 critical 0.3.6 09 Jul 2024
CVE-2024-39697: phonenumber - Panic on Parsing Crafted Phonenumber Inputs 8.6 high 0.3.6 07 Jul 2024
CVE-2023-42444: phonenumber panics on parsing crafted RF3966 inputs 7.5 high 0.2.5 21 Sep 2023

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 phonenumber

Is phonenumber safe to use?

Vulert records 4 vulnerabilities for phonenumber in crates.io: 1 critical, 1 high, 0 medium and 0 low, plus 2 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 phonenumber's Vulert package health score?

Vulert scores phonenumber 75/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 phonenumber affected?

No. 0.3.10+9.0.33, 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 phonenumber should I use?

0.3.10+9.0.33 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 phonenumber have?

4 vulnerabilities are recorded for phonenumber in the crates.io ecosystem: 1 critical, 1 high, 0 medium and 0 low, plus 2 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 phonenumber vulnerabilities disclosed?

0 vulnerabilities were recorded for phonenumber in the last 12 months, and the oldest entry in this database dates to 19 Sep 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 phonenumber 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 phonenumber for upcoming vulnerabilities?

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