VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/nyaruka/phonenumbers: vulnerability history, versions and safety

github.com/nyaruka/phonenumbers is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, from Sep 2025 to Nov 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 05 Nov 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/nyaruka/phonenumbers vulnerabilities

Vulert verdict on github.com/nyaruka/phonenumbers v1.8.1 i

Updated on 23 Oct 2026

Action needed: v1.8.1 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v1.8.1 — affected i
  • Vulnerabilities on record 2 over 1 year · 1 in the last year i
  • Latest disclosure 05 Nov 2025 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Stars 1,605 i
  • OpenSSF scorecard 3/10 i
  • Last release 3 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/nyaruka/phonenumbers, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v1.8.1 15 Jul 2026 M1 U1 MIT Yes Details →
v1.8.1-0.20260602230901-dd5e61152d6e 02 Jun 2026 M1 U1 MIT Yes Details →
v1.8.0 01 Jun 2026 M1 U1 MIT Yes Details →
v1.7.5 25 May 2026 M1 U1 MIT Yes Details →
v1.7.4 11 May 2026 M1 U1 MIT Yes Details →
v1.7.3 11 May 2026 M1 U1 MIT Yes Details →
v1.7.2 27 Apr 2026 M1 U1 MIT Yes Details →
v1.7.2-0.20260401192335-29eedcc6bbed 01 Apr 2026 M1 U1 MIT Yes Details →
v1.7.1 01 Apr 2026 M1 U1 MIT Yes Details →
v1.7.0 31 Mar 2026 M1 U1 MIT Yes Details →
v1.6.13 31 Mar 2026 M1 U1 MIT Yes Details →
v1.6.12 17 Mar 2026 M1 U1 MIT Yes Details →
v1.6.11 06 Mar 2026 M1 U1 MIT Yes Details →
v1.6.10 18 Feb 2026 M1 U1 MIT Yes Details →
v1.6.9 09 Feb 2026 M1 U1 MIT Yes Details →
v1.6.8 08 Jan 2026 M1 U1 MIT Yes Details →
v1.6.7 12 Nov 2025 M1 U1 MIT Yes Details →
v0.0.0-20251010134401-bd304b4da02f 10 Oct 2025 M1 U1 MIT Yes Details →
v1.6.6 10 Oct 2025 M1 U1 MIT Yes Details →
v1.6.5 11 Aug 2025 M1 U1 MIT Yes Details →
v1.6.4 22 Jul 2025 M1 U1 MIT Yes Details →
v1.6.3 22 May 2025 M1 U1 MIT Yes Details →
v1.6.3-0.20250522175334-84d5835d058a 22 May 2025 M1 U1 MIT Yes Details →
v1.6.2 22 May 2025 M1 U1 MIT Yes Details →
v1.6.1 23 Apr 2025 M1 U1 MIT Yes Details →
v1.6.0 20 Mar 2025 M1 U1 MIT Yes Details →
v0.0.0-20250320152610-a56545b699ea 20 Mar 2025 M1 U1 MIT Yes Details →
v1.5.1-0.20250320152237-a95561d0d84b 20 Mar 2025 M1 U1 MIT Yes Details →
v1.5.0 18 Jan 2025 M1 U1 MIT Yes Details →
v1.4.5-0.20250117215908-a1a3a1912f2d 17 Jan 2025 M1 U1 MIT Yes Details →
v1.4.5-0.20241224131822-b99b59baaf6e 24 Dec 2024 M1 U1 MIT Yes Details →
v1.4.4 20 Dec 2024 M1 U1 MIT Yes Details →
v1.4.3 29 Nov 2024 M1 U1 MIT Yes Details →
v1.4.2 15 Nov 2024 M1 U1 MIT Yes Details →
v1.4.1 16 Oct 2024 M1 U1 MIT Yes Details →
v1.4.1-0.20240726143403-a488bc228d4f 26 Jul 2024 M1 U1 MIT Yes Details →
v1.4.1-0.20240723152857-123ee78610f3 23 Jul 2024 M1 U1 MIT Yes Details →
v1.4.0 15 Jul 2024 M1 U1 MIT Yes Details →
v1.3.7-0.20240528163540-cbd7e92d0cdb 28 May 2024 M1 U1 MIT Yes Details →
v1.3.7-0.20240527150318-8685480e95ac 27 May 2024 M1 U1 MIT Yes Details →
v1.3.7-0.20240527145838-cd85a6c2e616 27 May 2024 M1 U1 MIT Yes Details →
v1.3.6 27 May 2024 M1 U1 MIT Yes Details →
v0.0.0-20240508155333-a90ed92a777e 08 May 2024 M1 U1 MIT Yes Details →
v1.3.5 08 May 2024 M1 U1 MIT Yes Details →
v0.0.0-20240314151729-905e39d0ae7e 14 Mar 2024 M1 U1 MIT Yes Details →
v1.3.4 14 Mar 2024 M1 U1 MIT Yes Details →
v1.3.3 13 Mar 2024 M1 U1 MIT Yes Details →
v0.0.0-20240218170404-bf4a755670bd 18 Feb 2024 M1 U1 MIT Yes Details →
v1.3.2 18 Feb 2024 M1 U1 MIT Yes Details →
v0.0.0-20240126180032-6c888c166432 26 Jan 2024 M1 U1 MIT Yes Details →
v1.3.1 26 Jan 2024 M1 U1 MIT Yes Details →
v0.0.0-20231214210057-718b0c4d7422 14 Dec 2023 M1 U1 MIT Yes Details →
v1.3.0 14 Dec 2023 M1 U1 MIT Yes Details →
v1.2.3 12 Dec 2023 M1 U1 MIT Yes Details →
v1.2.2 24 Nov 2023 M1 U1 MIT Yes Details →
v1.2.2-0.20231124204749-0479e35488e8 24 Nov 2023 M1 U1 MIT Yes Details →
v1.2.1 20 Nov 2023 M1 U1 MIT Yes Details →
v1.2.0 17 Nov 2023 M1 U1 MIT Yes Details →
v1.1.9 08 Nov 2023 M1 U1 MIT Yes Details →
v1.1.8 09 Aug 2023 M1 U1 MIT Yes Details →
v0.0.0-20230510104958-66d5c5576281 10 May 2023 M1 U1 MIT Yes Details →
v1.1.7 10 May 2023 M1 U1 MIT Yes Details →
v1.1.7-0.20230223142803-57673436d001 23 Feb 2023 M1 U1 MIT Yes Details →
v1.1.6 13 Feb 2023 M1 U1 MIT Yes Details →
v1.1.5 27 Jan 2023 M1 U1 MIT Yes Details →
v1.1.4 28 Nov 2022 M1 U1 MIT Yes Details →
v1.1.3 28 Nov 2022 M1 U1 MIT Yes Details →
v1.1.2 27 Oct 2022 M1 U1 MIT Yes Details →
v0.0.0-20221026145545-a758bdf3899d 26 Oct 2022 M1 U1 MIT Yes Details →
v1.1.2-0.20221026145545-a758bdf3899d 26 Oct 2022 M1 U1 MIT Yes Details →
v0.0.0-20220919160141-443d55916ec0 19 Sep 2022 M1 U1 MIT Yes Details →
v1.1.2-0.20220919160141-443d55916ec0 19 Sep 2022 M1 U1 MIT Yes Details →
v1.1.1 26 Aug 2022 M1 U1 MIT Yes Details →
v1.1.1-0.20220718211329-4eb911215f9b 18 Jul 2022 M1 U1 MIT Yes Details →
v1.1.0 22 Jun 2022 M1 U1 MIT Yes Details →
v1.0.76-0.20220609210528-d9769c34d183 09 Jun 2022 M1 U1 MIT Yes Details →
v1.0.75 02 May 2022 M1 U1 MIT Yes Details →
v1.0.75-0.20220502150214-bc25d9333e93 02 May 2022 M1 U1 MIT Yes Details →
v1.0.74 03 Jan 2022 M1 U1 MIT Yes Details →
v1.0.74-0.20220103202518-4be5829e6e4f 03 Jan 2022 M1 U1 MIT Yes Details →
v1.0.73 25 Oct 2021 M1 U1 MIT Yes Details →
v1.0.72 05 Oct 2021 M1 U1 MIT Yes Details →
v1.0.72-0.20210826145853-4e1a79c086b3 26 Aug 2021 M1 U1 MIT Yes Details →
v1.0.71 26 Aug 2021 M1 U1 MIT Yes Details →
v0.0.0-20210609175742-89eb84fbd0e7 09 Jun 2021 M1 U1 MIT Yes Details →
v1.0.70 09 Jun 2021 M1 U1 MIT Yes Details →
v0.0.0-20210505141045-449afadd8858 05 May 2021 M1 U1 MIT Yes Details →
v1.0.69 05 May 2021 M1 U1 MIT Yes Details →
v1.0.68 17 Mar 2021 M1 U1 MIT Yes Details →
v1.0.67 15 Mar 2021 M1 U1 MIT Yes Details →
v1.0.67-0.20210304195755-1e2bf123daa6 04 Mar 2021 M1 U1 MIT Yes Details →
v1.0.66 08 Feb 2021 M1 U1 MIT Yes Details →
v1.0.65 29 Jan 2021 M1 U1 MIT Yes Details →
v1.0.64 28 Jan 2021 M1 U1 MIT Yes Details →
v1.0.63 28 Jan 2021 M1 U1 MIT Yes Details →
v1.0.62 28 Jan 2021 M1 U1 MIT Yes Details →
v1.0.61 15 Jan 2021 M1 U1 MIT Yes Details →
v1.0.60 02 Dec 2020 M1 U1 MIT Yes Details →
v1.0.60-0.20201202104058-3c618720a762 02 Dec 2020 M1 U1 MIT Yes Details →
v1.0.59 19 Oct 2020 M1 U1 MIT Yes Details →
v1.0.58 12 Oct 2020 M1 U1 — Yes Details →
v1.0.58-0.20201012153545-eea6a12868cb 12 Oct 2020 M1 U1 — Yes Details →
v1.0.57 03 Aug 2020 M1 U1 — Yes Details →
v1.0.56 12 Jun 2020 M1 U1 — Yes Details →
v1.0.55 13 Apr 2020 M1 U1 — Yes Details →
v1.0.54 10 Dec 2019 M1 U1 — Yes Details →
v1.0.53 18 Nov 2019 M1 U1 — Yes Details →
v1.0.53-0.20191118172119-89cd4ea48573 18 Nov 2019 M1 U1 — Yes Details →
v1.0.52 23 Oct 2019 M1 U1 — Yes Details →
v1.0.51 17 Oct 2019 M1 U1 — Yes Details →
v1.0.50 06 Oct 2019 M1 U1 — Yes Details →
v0.0.0-20190918145249-ce4687a3c367 18 Sep 2019 M1 U1 — Yes Details →
v1.0.49 18 Sep 2019 M1 U1 — Yes Details →
v1.0.48 18 Sep 2019 M1 U1 — Yes Details →
v1.0.47 18 Sep 2019 M1 U1 — Yes Details →
v1.0.46 18 Sep 2019 M1 U1 — Yes Details →
v1.0.46-0.20190918102820-55a72cfa0597 18 Sep 2019 M1 U1 — Yes Details →
v1.0.45 02 Sep 2019 M1 U1 — Yes Details →
v1.0.44 06 Aug 2019 M1 U1 — Yes Details →
v1.0.43 20 Jun 2019 M1 U1 — Yes Details →

The newest 120 of 178 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/nyaruka/phonenumbers

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-10954: github.com/nyaruka/phonenumbers Vulnerable to Improper Input Validation 5.3 medium 1.2.2 27 Sep 2025
CVE-2025-10954: Vulnerability in github.com/nyaruka/phonenumbers - Improper Input Validation N/A unrated 1.2.2 05 Nov 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/nyaruka/phonenumbers

Is github.com/nyaruka/phonenumbers safe to use?

Vulert records 2 vulnerabilities for github.com/nyaruka/phonenumbers in Go: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/nyaruka/phonenumbers's Vulert package health score?

Vulert scores github.com/nyaruka/phonenumbers 78/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of github.com/nyaruka/phonenumbers affected?

Yes. v1.8.1, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/nyaruka/phonenumbers should I use?

v1.8.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/nyaruka/phonenumbers have?

2 vulnerabilities are recorded for github.com/nyaruka/phonenumbers in the Go ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/nyaruka/phonenumbers vulnerabilities disclosed?

1 vulnerability was recorded for github.com/nyaruka/phonenumbers in the last 12 months, and the oldest entry in this database dates to 27 Sep 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of github.com/nyaruka/phonenumbers are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor github.com/nyaruka/phonenumbers for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/nyaruka/phonenumbers version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.