nyaruka phonenumbers up to 1.2.1 phonenumbers.Parse improper validation of syntactic correctness of input
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in nyaruka phonenumbers up to 1.2.1. This impacts the function phonenumbers.Parse. Executing a manipulation can lead to improper validation of syntactic correctness of input.
This vulnerability is registered as CVE-2025-10954. It is possible to launch the attack remotely. No exploit is available.
Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic was found in nyaruka phonenumbers up to 1.2.1. This vulnerability affects the function phonenumbers.Parse. The manipulation with an unknown input leads to a improper validation of syntactic correctness of input vulnerability. The CWE definition for the vulnerability is CWE-1286. The product receives input that is expected to be well-formed - i.e., to comply with a certain syntax - but it does not validate or incorrectly validates that the input complies with the syntax. As an impact it is known to affect availability. CVE summarizes:
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".
The advisory is available at security.snyk.io. This vulnerability was named CVE-2025-10954 since 09/25/2025. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit.
Upgrading to version 1.2.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-31408). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 6.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔒
CNA Base Score: 5.3
CNA Vector (snyk): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper validation of syntactic correctness of inputCWE: CWE-1286 / CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Proof-of-Concept
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: phonenumbers 1.2.2
Timeline
09/25/2025 CVE reserved09/27/2025 Advisory disclosed
09/27/2025 VulDB entry created
10/03/2025 VulDB entry last update
Sources
Advisory: SNYK-GOLANG-GITHUBCOMNYARUKAPHONENUMBERS-6084070Status: Confirmed
CVE: CVE-2025-10954 (🔒)
GCVE (CVE): GCVE-0-2025-10954
GCVE (VulDB): GCVE-100-326170
EUVD: 🔒
Entry
Created: 09/27/2025 07:17Updated: 10/03/2025 23:42
Changes: 09/27/2025 07:17 (77), 09/27/2025 07:47 (2), 09/27/2025 10:40 (1), 10/03/2025 23:42 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.