CVE-2024-39891: Twilio Authy Information Disclosure
Twilio Authy · listed in the CISA catalog of actively exploited vulnerabilities since 2024-07-23.
- CVSS v3.1 (CVE record)
- 5.3
- medium
- EPSS (exploit probability, 30 days)
- 1.7%
- higher than 77.3% of all CVEs
- Added to CISA KEV
- 2024-07-23
- US federal due date 2024-08-13
- Automatable (CISA SSVC)
- yes
- technical impact: partial
CVE-2024-39891 explained
CVE-2024-39891 is an information disclosure flaw in the Twilio Authy API, used by Authy Android and Authy iOS. An unauthenticated endpoint revealed whether submitted phone numbers were registered with Authy. It was exploited in the wild in June 2024 and is listed in CISA's Known Exploited Vulnerabilities catalog.
Impact
A remote, unauthenticated attacker could send a stream of phone numbers to the endpoint and learn which ones were registered with Authy. No user interaction or privileges were needed. CISA rates it automatable, meaning it can be exploited at scale, with partial technical impact. Only confidentiality is affected, at a limited level. According to the description, Authy accounts were not compromised.
Who is affected
The description names Authy Android before 25.1.0 and Authy iOS before 26.1.0, both of which accessed the affected Twilio Authy API. The CVE record lists twilio authy_2-factor_authentication with the ranges < 25.1.0 and < 26.1.0, based on CISA's CPE enrichment. The CVE record names no fixed version. The ranges suggest Android 25.1.0 and iOS 26.1.0 as the first unaffected releases, but check the vendor advisory to confirm.
Written with AI from the data on this page and checked against it automatically.
Official 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.)
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
CISA notes
Affected and fixed versions
Version ranges from CISA's enrichment of the CVE record (CPE-based); the record itself lists none.
- twilio authy_2-factor_authenticationAffectedFixed in
- < 25.1.0
- < 26.1.0
not statedVersion ranges from CISA ADP enrichment (CPE-based); the CNA record has none.
| Product | Affected | Fixed in |
|---|---|---|
| twilio authy_2-factor_authenticationVersion ranges from CISA ADP enrichment (CPE-based); the CNA record has none. |
| not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: twilio.com/docs/usage/security/reporting-vulnerabilities
- CISA's deadline for US federal agencies: 2024-08-13 (passed) – a useful benchmark for everyone else, too.
What to do
- Update Authy Android to
25.1.0or later and Authy iOS to26.1.0or later on all managed devices. - Follow the Twilio vendor advisory and apply any mitigations it describes.
- Use mobile device management to enforce minimum Authy app versions across your fleet.
- Meet CISA's required action: apply vendor mitigations, or discontinue use if mitigations are unavailable.
The CVE record names no fixed version, although the description indicates that Authy Android 25.1.0 and Authy iOS 26.1.0 are no longer affected. Confirm this in the Twilio vendor advisory. Follow CISA's required action: apply mitigations per vendor instructions, or discontinue use of the product if mitigations are unavailable.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Partial – limited control or information
Weakness: CWE-203 Observable Discrepancy
Questions about CVE-2024-39891
- Were Authy accounts compromised?
- No. The description states that Authy accounts were not compromised. The flaw only revealed whether a given phone number was registered with Authy.
- Is this vulnerability being exploited?
- Yes. The description says it was exploited in the wild in June 2024. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-07-23, with a US federal due date of 2024-08-13.
- Which app versions should users run?
- The description names Authy Android before
25.1.0and Authy iOS before26.1.0as affected. Users should run at least those versions. The CVE record itself names no fixed version, so confirm in the vendor advisory.
Written with AI from the data on this page and checked against it automatically.
References
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.