High · CVSS 8.6CVE-2024-39697GHSA-MJW4-JJ88-V687

phonenumber: panic on parsing crafted phonenumber inputsCVE-2024-39697

Answer in brief

CVE-2024-39697 records a High severity (CVSS 8.6) vulnerability in phonenumber: panic on parsing crafted phonenumber inputs. The current sources do not mark it as known exploited. The current feed maps phonenumber (crates.io). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Jul 7, 2024Updated Oct 12, 2026Source checked Oct 12, 2026First seen by HOL Oct 12, 2026Material review Oct 12, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.6
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 8.6. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps phonenumber (crates.io). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
phonenumbercrates.io	>=0.3.3 <0.3.6	0.3.6

Recommended response

Check inventory. Check lockfiles and deployed manifests for phonenumber.
Review the reported fix. Update phonenumber to 0.3.6 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Jul 7, 2024
Evidence: source:osv:source_dates:source-dates:record
Source modified
Oct 12, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Oct 12, 2026

Sources and claim methodology

Upstream source description

### Impact The phonenumber parsing code may panic due to a reachable `assert!` guard on the phonenumber string. In a typical deployment of rust-phonenumber, this may get triggered by feeding a maliciously crafted phonenumber, e.g. over the network, specifically strings of the form `+dwPAA;phone-context=AA`, where the "number" part potentially parses as a number larger than 2^56. Since f69abee1/0.3.4/#52. 0.2.x series is not affected. ### Patches Patches have been published as version `0.3.6+8.13.36`.

Quoted source text, attributed separately from HOL analysis.