Description
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.)
No analysis available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
No advisories yet.
References
History
Tue, 21 Oct 2025 23:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Tue, 21 Oct 2025 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Tue, 21 Oct 2025 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Wed, 30 Jul 2025 02:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Twilio authy 2-factor Authentication
|
|
| CPEs | cpe:2.3:a:twilio:authy_2-factor_authentication:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Twilio authy 2-factor Authentication
|
|
| Metrics |
ssvc
|
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2025-10-21T22:55:50.240Z
Reserved: 2024-07-02T00:00:00.000Z
Link: CVE-2024-39891
Updated: 2024-08-02T04:33:11.402Z
Status : Analyzed
Published: 2024-07-02T18:15:03.447
Modified: 2025-11-05T19:11:21.007
Link: CVE-2024-39891
No data.
OpenCVE Enrichment
No data.
Weaknesses