⚠ Known Exploited Vulnerability (KEV) Tracker

Description

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.

Lifecycle Timeline

• 2024-07-02
  CVE published

  Entered the public CVE record.

  CVE.org →
• 2024-07-23
  Added to CISA KEV 21 days later

  Listed as known exploited, which starts the federal remediation clock.

  CISA KEV →
• 2024-07-27
  EPSS flags exploitation risk 4 days later

  Probability rose past 10%, from 0.0% to 11.8%. Dated to the sampled week.

  FIRST EPSS →
• 2024-08-13
  Federal remediation due 17 days later

  Deadline for federal civilian agencies under BOD 22-01 — now passed.

  CISA KEV
• not recorded
  Public exploit code

  No dated exploit found in Metasploit, Exploit-DB or public GitHub repositories.
• not recorded
  First national advisory

  No tracked government advisory analyses this CVE. Routine KEV catalog-addition alerts do not count here.
• not recorded
  Vendor fix published

  No dated vendor fix. Only Microsoft publishes a machine-readable release date; other vendors state a fixed version without one.

Each milestone comes from a different source, so gaps between them are gaps in what those sources publish, not evidence that nothing happened. EPSS history for this CVE holds 128 points from 2024-07-06, tracked daily from 2026-09-09; earlier points are weekly, which dates a spike to within a week. Peak probability 51.4% on 2025-03-29.

Published Applicability

Check whether a specific version is affected →

What each source publishes about which product versions carry this vulnerability, kept as written rather than merged. Absence here means no source has published applicability data, not that nothing is affected.

Research & News Coverage

No mentions found in monitored research blogs or news feeds.

Detection & Exploitation

Blind spot. No public detection — verify by version/patch. Nothing in the monitored scanner, IDS, SIEM or offensive-tool collections references this CVE, so exposure has to be established from asset inventory and patch level rather than from a signature.

Coverage across public collections only: Nuclei and OpenVAS NVT (scan); Snort and Suricata ET Open (network); Sigma and YARA (host/SIEM); Metasploit, Exploit-DB and public GitHub repositories (exploit). Absence here means nothing public was found, not that detection is impossible.
GitHub PoC repositories are collected automatically by PoC-in-GitHub (CC0) and are not vetted: some are fakes and some are malware. Treat them as evidence that code was published, not as code to run.
OpenVAS coverage derives from the Greenbone Community Feed, made available under the Open Database License (ODbL) v1.0; its individual Vulnerability Tests are licensed GNU GPL v2.

CISA Assessment (Vulnrichment / SSVC)

KEV Catalog Status

Listed By

Weaponization Timeline — Offensive & Testing Tools

No exploit-tool sightings recorded for this CVE.

Evidence tiers are explained on the About page — a merged Metasploit module is far stronger evidence than a distro package mention.

External References

CVE.org record → NVD entry → CISA KEV catalog → FortiGuard Labs → Rapid7 AttackerKB →