Advisory record · GHSA-whhr-7f2w-qqj2

phonenumber: panic on parsing crafted RF3966 phonenumber inputs

CVSS 8.6 HighEPSS 0.0087 · 58th percentile

Published by the GitHub Advisory Database at 19 Sept 2023, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
phonenumbercrates.io>=0.0.0-0, <0.2.5 || >=0.3.0, <0.3.30.2.5, 0.3.3
Identifiers
GHSA-whhr-7f2w-qqj2 · CVE-2023-42444 · RUSTSEC-2023-0082
Weakness (CWE)
CWE-248 · CWE-392 · CWE-1284
Published
19 Sept 2023
Updated
13 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The phonenumber crate before 0.2.5, and versions 0.3.0 through 0.3.2, can panic when parsing a maliciously crafted RFC 3966 phone number. In a typical deployment, a remote attacker can trigger this by sending such input over the network, which causes the parser to panic. Upgrade to phonenumber 0.2.5 or 0.3.3.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.6 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0087, the 58th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 31 Oct 2026, 14:24 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.