How severe is CVE-2025-10954?

No CVSS score has been assigned to CVE-2025-10954 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-10954?

CVE-2025-10954 affects the following packages: github.com/nyaruka/phonenumbers (Go). Ecosystems affected: Go.

How do I fix CVE-2025-10954?

Update github.com/nyaruka/phonenumbers to 1.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-10954 is resolved across your whole dependency graph.

How do I detect CVE-2025-10954 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/nyaruka/phonenumbers, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-10954 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2025-10954 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-10954 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-10954?

CVE-2025-10954 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-10954?

CVE-2025-10954 is classified as CWE-1286 (CWE-1286). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-10954 published, and has it been updated?

CVE-2025-10954 was published on September 27, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2025-10954 — phonenumbers

Fix: nyaruka/phonenumbers@0479e35

CVE-2025-10954 is a CWE-1286 vulnerability in github.com/nyaruka/phonenumbers. A fix is available for github.com/nyaruka/phonenumbers — see the affected versions and patch details below.

github.com/nyaruka/phonenumbers Vulnerable to Improper Validation of Syntactic Correctness of Input

Also known asGHSA-fmjh-f678-cv3xGO-2025-3987

Published

Sep 27, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-10954.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/nyaruka/phonenumbers

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Versions of the package github.com/nyaruka/phonenumbers before 1.2.2 are vulnerable to Improper Validation of Syntactic Correctness of Input in the phonenumbers.Parse() function. An attacker can cause a panic by providing crafted input causing a "runtime error: slice bounds out of range".

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/nyaruka/phonenumbers`	all versions	1.2.2`go get github.com/nyaruka/phonenumbers@v1.2.2`

Affected Products

1 product · 1 configurations

Application

phonenumberstextit

< 1.2.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/nyaruka/phonenumbers, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/nyaruka/phonenumbers to 1.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-10954 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-10954 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works