CVE-2026-4984
Webhook accepts unsigned POSTs; attacker can steal Twilio credentials.
Is CVE-2026-4984 being exploited?
Not confirmed. CVE-2026-4984 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.16% probability of exploitation in the next 30 days.
How severe is CVE-2026-4984?
CVE-2026-4984 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-4984?
Not known from our data. No patch reference has been recorded for CVE-2026-4984, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-4984 affect?
CVE-2026-4984 affects Twilio, Twilio Webhook, Twilio integration. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-4984?
Enable signature validation; restrict MediaUrlN; rotate credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker forges webhook to exfiltrate Twilio accountSID and authToken via Basic Auth, enabling full account takeover.
Immediate action required