CVE-2024-39891
Twilio — Twilio Authy Information Disclosure Vulnerability
Twilio · CWE-203 · in CISA KEV since 2024-07-23
EVRS 75 of 100 Urgent
Patch This Cycle
Rank 1,254 of 2,960 tracked
Raised to the floor for a confirmed exploited vulnerability.
Why it scores 75
Evidence available: 6 of 7 signalsListed in the CISA KEV catalog, and an EPSS probability of 0.017.
- CISA KEVApplied
- RansomwareDid not apply
- Vendor exploitationDid not apply
- EPSSApplied
- Microsoft Exploitability IndexNot applicable
- Pre-patch disclosureNo data
- KEV recencyDid not apply
- CVSSApplied
The band answers “how soon”, not “how bad”. No data for: Pre-patch disclosure. Why some signals show no data
Fix
Patch or fixed version identifiedCISA required action
Fixed in
authy: update to 26.1.0 or later | authy authenticator: update to 25.1.0 or later
Affected versions
- authy
< 26.1.0 - authy authenticator
< 25.1.0
Remediation
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Fixed versions from NVD.
Evidence
Each value with its source| Measure | Value | Source |
|---|---|---|
| CVSS base scoreHow severe the flaw is in itself. It does not say how likely an attack is. | 5.3 | NVD |
| FIRST EPSSFIRST's estimate of the chance this is exploited in the next 30 days, and how that ranks against all CVEs. | 0.017 (76.6th pctl) | FIRST EPSS |
| Actively exploitedWhether a source of record has confirmed attacks using it in the wild. | Confirmed | CISA KEV |
| Ransomware campaign useWhether CISA has seen ransomware operators use it. | Unknown or none | CISA KEV |
| CISA remediation deadlineThe date US federal agencies must have fixed or mitigated it. | 2024-08-13 · KEV since 2024 · listed over a year | CISA KEV |
| Public exploit moduleA module existing is not the same as active exploitation. | None known | Metasploit |
| EUVD cross-referenceENISA's record: CVSS 5.3 (v3.1), assigned by mitre. | Listed | ENISA EUVD |
Description
NVDIn 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.)
What CISA says to do