Live › vulnerability › CVE-2024-39891
Go to dashboardTwilio Authy has an API endpoint that needs no login and tells the caller whether a given phone number is registered with Authy. An attacker can use it to check phone numbers against the Authy user base, which is a privacy leak and aids phishing or targeting.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 3h before NVD. All times on this page are UTC.
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| twilio authy | vendor | < 26.1.0 | 26.1.0 |
| twilio authy authenticator | vendor | < 25.1.0 | 25.1.0 |
| Twilio Authy | vendor | – | – |
Unknown from the sources.
Apply mitigations per vendor instructions, or discontinue use of Authy if mitigations are unavailable (per CISA required action).
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Twilio Authy API, accessed by Authy Android before 25.1.0 and Authy iOS before 26.1.0, an unauthenticated endpoint provided access to certain phone-number data, as exploited in the wild in June 2024. Specifically, the endpoint accepted a stream of requests containing phone numbers, and responded with information about whether each phone number was registered with Authy. (Authy accounts were not compromised, however.)
This page as .md · .json · in your agent: get_signal("CVE-2024-39891")
CISA KEV catalog, Creative Commons 0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.