CVE-2024-39891
Exploited in the wild. In CISA KEV since 2024‑07‑23. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- Twilio AuthyAffected: < 26.1.0Upgrade to: 26.1.0Stated by: NVD
- Twilio Authy AuthenticatorAffected: < 25.1.0Upgrade to: 25.1.0Stated by: NVD
Versions as the sources state them. Full version matrix after sign-in
Coverage timeline
0 publishersAdded to CISA KEV catalog
Sourced from public security reporting — each date is when it was published, not when it happened.
What it is
From the CVE record
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.)
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Listed as exploited in the wild since 2024-07-23.
US federal agencies must remediate by 2024-08-13.
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
1.7% chance of exploitation activity in the next 30 days, which ranks it in the 77th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
- Attention now
Sustained.
Lifecycle
7 events over 720 days, from the signal feeds we watch.
- EPSS band changemoderate → low
- Patch availablerecord updated
- Added to CISA KEV
- Publishedweakness classified, att&ck mapped
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Scored 5.3 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality LowSome restricted information is disclosed, but limited in scope
- Integrity NoneNo integrity impact
- Availability NoneNo availability impact
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
- cwe.mitre.org/data/definitions/203.html
- twilio.com/docs/usage/security/reporting-vulnerabilities
- twilio.com/en-us/changelog
And 8 more references. See all after sign-in
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Authy, not every advisory. This one: actively exploited.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI