Authy 2 Factor Authentication
Approved changes feed: RSS · Atom
cpe:2.3:a:twilio:authy_2-factor_authentication:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Twilio (967eb3e1-96f4-5f82-91e8-30cd1fcf46ac) |
|---|---|
| Product | Authy 2 Factor Authentication (cc981634-7c01-5388-a92d-7b7649532753) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/twilio/authy-java |
purl2cpe | 2026-06-01 10:12:06.117262 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-39891 |
vulnerable | 2026-06-08 06:41:51.789460 |
Details available
MEDIUM (5.3)
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.)
Published: 2024-07-02T00:00:00.000Z
Updated: 2025-10-21T22:55:50.240Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.