dbcve.org
WhatsappApplication

CVE-2019-11927

HIGH · 7.8 CVSS v3.1 Published 2019-09-27
Fix available
A fix is available. Upgrade to 2.9.143 / 2.19.100 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An integer overflow in WhatsApp media parsing libraries allows a remote attacker to perform an out-of-bounds write on the heap via specially-crafted EXIF tags in WEBP images. This issue affects WhatsApp for Android before version 2.19.143 and WhatsApp for iOS before version 2.19.100.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An integer overflow vulnerability exists in WhatsApp's media parsing libraries when processing EXIF metadata in WEBP images. The overflow allows a remote attacker to perform an out-of-bounds write on the heap, potentially enabling arbitrary code execution.

MitigationUpdate WhatsApp for Android to version 2.19.143 or later, and WhatsApp for iOS to version 2.19.100 or later.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WhatsappApplication
Affected:< 2.9.143< 2.19.100

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your WhatsApp platform
    Determine whether you have WhatsApp installed on Android or iOS. Check your device settings or the app icon to confirm the platform.
    Affected if Platform is Android or iOS - this CVE affects both mobile clients
  2. Check WhatsApp for Android version
    Open WhatsApp, tap the three-dot menu, go to Settings > Help > App Info. Alternatively, open Google Play Store, search for WhatsApp, and view the version number under the app listing.
    Affected if Version is less than 2.19.143 (for Android)
  3. Check WhatsApp for iOS version
    Open WhatsApp, go to Settings > Help > App Info. Alternatively, open the App Store, search for WhatsApp, and view the version number under the app listing.
    Affected if Version is less than 2.19.100 (for iOS)

You are affected if you have WhatsApp for Android version below 2.19.143 or WhatsApp for iOS version below 2.19.100, and you receive or process WEBP images through the application.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 2.9.143 / 2.19.100 or later
Fixed in 2.9.1432.19.100
Interim mitigation

Update WhatsApp for Android to version 2.19.143 or later, and WhatsApp for iOS to version 2.19.100 or later.

Fix this in Whatsapp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-11927 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-11927 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data