CVE-2025-13166

LOWPre-NVD 3.73.7
EchelonGraph scoreHIGH confidence

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-09-15. a secondary CVSS source baseline 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The SMS OTP flow fails to adequately handle error messages, allowing an attacker to infer the existence of registered user accounts based on the responses received during the OTP initiation process.

This weakness can be exploited by an attacker to discover valid usernames within the system. The impact is amplified for accounts that have not configured a mobile number, as the enumeration is specifically tied to this condition. The discovery of these usernames can facilitate subsequent brute force attacks, social engineering attempts, and information leakage, potentially leading to reputational damage, loss of customer trust, and regulatory non-compliance.

CVSS v3
3.7
EG Score
3.7(high)
EG Risk
17(Track)
EG Risk 17/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity37% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 18, 2026

Vendor Advisories for CVE-2025-13166(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:29 UTCEG score recompute
  2. 2026-09-18 19:29 UTCGHSA enrichment
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-16 14:06 UTCEPSS rescore
  5. 2026-09-16 05:13 UTCEPSS rescore
  6. 2026-09-15 23:21 UTCEG score recompute
  7. 2026-09-15 23:21 UTCGHSA enrichment
  8. 2026-09-15 22:28 UTCEG score recompute
  9. 2026-09-15 22:28 UTCGHSA enrichment
  10. 2026-09-15 13:33 UTCEG score recompute
  11. 2026-09-15 13:33 UTCGHSA enrichment
  12. 2026-09-15 12:53 UTCEG score recompute
  13. 2026-09-15 12:53 UTCGHSA enrichment
  14. 2026-09-15 10:28 UTCEG score recompute
  15. 2026-09-15 09:58 UTCEG score recompute
  16. 2026-09-15 09:57 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2025-13166?
CVE-2025-13166 is a low vulnerability published on September 15, 2026. The SMS OTP flow fails to adequately handle error messages, allowing an attacker to infer the existence of registered user accounts based on the responses received during the OTP initiation process. This weakness can be exploited by an attacker to discover valid usernames within the system. The…
When was CVE-2025-13166 disclosed?
CVE-2025-13166 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-13166 actively exploited?
CVE-2025-13166 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.5% of all scored CVEs.
What is the CVSS score of CVE-2025-13166?
CVE-2025-13166 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2025-13166?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-13166, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-13166

Explore →

Is Your Infrastructure Affected by CVE-2025-13166?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.