# phonenumber: panic on parsing crafted RF3966 phonenumber inputs

Advisory record · `GHSA-whhr-7f2w-qqj2`

- **Identifiers:** `GHSA-whhr-7f2w-qqj2` · `CVE-2023-42444` · `RUSTSEC-2023-0082`
- **State:** Confirmed
- **Severity:** CVSS 8.6 High
- **Critical:** No
- **Weakness (CWE):** [CWE-248](https://cwe.mitre.org/data/definitions/248.html) · [CWE-392](https://cwe.mitre.org/data/definitions/392.html) · [CWE-1284](https://cwe.mitre.org/data/definitions/1284.html)
- **Tags:** [CWE-248](https://agentprime.io/advisories/tag/cwe-248.md) · [CWE-392](https://agentprime.io/advisories/tag/cwe-392.md) · [CWE-1284](https://agentprime.io/advisories/tag/cwe-1284.md)
- **Published:** 19 Sept 2023
- **Updated:** 13 Oct 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `phonenumber` (crates.io): affected `>=0.0.0-0, <0.2.5 || >=0.3.0, <0.3.3`; fixed in `0.2.5`, `0.3.3`

## 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

- 8.6 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0087, the 58th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:24 UTC: First seen by agentprime
- 31 Oct 2026, 14:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/RUSTSEC-2023-0082)

## Sources

- [GitHub Advisory Database: GHSA-whhr-7f2w-qqj2](https://github.com/advisories/GHSA-whhr-7f2w-qqj2)
- [OSV: GHSA-whhr-7f2w-qqj2](https://osv.dev/vulnerability/GHSA-whhr-7f2w-qqj2)
- <https://crates.io/crates/phonenumber>
- <https://rustsec.org/advisories/RUSTSEC-2023-0082.html>
- <https://github.com/whisperfish/rust-phonenumber/commit/2dd44be94539c051b4dee55d1d9d349bd7bedde6>
- <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-42444>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-whhr-7f2w-qqj2>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-whhr-7f2w-qqj2/>. Everything for agents: <https://agentprime.io/llms.txt>.