Twilio Authy Information Disclosure Vulnerability
CVE-2024-39891
How serious is it
- Severity: not rated yet.
- No exploit prediction (EPSS) score yet.
- Confirmed exploited in the wild (CISA KEV).
- No public exploit in Exploit-DB.
Is your app affected by CVE-2024-39891?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Twilio Authy
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
Twilio Authy contains an information disclosure vulnerability in its API that allows an unauthenticated endpoint to accept a request containing a phone number and respond with information about whether the phone number was registered with Authy.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- No references listed.
Merged from CISA KEV. Last updated 24 Oct 2026. All vulnerabilities · RSS · JSON