Skip to content

CVE-2019-3568

A buffer overflow vulnerability in WhatsApp VOIP stack allowed remote code execution via specially crafted series of RTCP packets sent to a target phone number. The issue affects WhatsApp for Android prior to v2.19.134, WhatsApp Business for Android prior to v2.19.44, WhatsApp for iOS prior to v2.19.51, WhatsApp Business for iOS prior to v2.19.51, WhatsApp for Windows Phone prior to v2.18.348, and WhatsApp for Tizen prior to v2.18.15.

CVSS
9.8Criticalscored by CISA
Exploited in the wild
Yes, in CISA KEV since 19 Apr 2022CISA deadline for US federal agencies: 10 May 2022
EPSS
30.1%chance of exploitation in the next 30 daystop 2% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
14 May 2019analysed here 12 Nov 2026

Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weaknesses
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Facebook WhatsApp Business for Android2.19.44< 2.19.134Vendor says fixed in: not stated
Facebook WhatsApp Business for iOS2.19.51< 2.19.51Vendor says fixed in: not stated
Facebook WhatsApp for Android2.19.134< 2.19.134Vendor says fixed in: not stated
Facebook WhatsApp for iOS2.19.51< 2.19.51Vendor says fixed in: not stated
Facebook WhatsApp for Tizen2.18.15< 2.18.15Vendor says fixed in: not stated
Facebook WhatsApp for Windows Phone2.18.348< 2.18.348Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • whatsapp:whatsapp
  • whatsapp:whatsapp_business

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. This is a heap buffer overflow. Generic WAF rules do not recognise the input that triggers it; only a rule written for this specific CVE can, and only if the triggering request has a recognisable shape.

Also consider: patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 19 Apr 2022.
CISA due date
10 May 2022, the remediation deadline for US federal agencies
CISA required action
Apply updates per vendor instructions.
Public exploit code
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
CISA SSVC
exploitation active, automatable yes, technical impact totalAssessed by CISA 7 Feb 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Timeline

  1. 14 May 2019Published
  2. 19 Apr 2022Added to CISA KEV (exploited in the wild)1,070 days (about 3 years) later
  3. 10 May 2022CISA remediation due date (US federal agencies)21 days later
  4. 7 Feb 2025CISA SSVC assessment: exploitation active1,005 days (about 3 years) later
  5. 21 Oct 2025CVE record last updated256 days (about 9 months) later
  6. 12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2019-3568 being exploited?

Yes. CVE-2019-3568 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2019-3568?

CVE-2019-3568 is rated Critical with a CVSS score of 9.8. 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-2019-3568?

Yes. A fix has been recorded for CVE-2019-3568. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2019-3568 affect?

CVE-2019-3568 affects whatsapp:whatsapp, whatsapp:whatsapp_business. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

3 references in the CVE record, grouped by the tags the record gives them.

Other links (3)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com