Skip to main content
Menu
CVEs

Facebook WhatsApp Business for Android SQL injection in order details message parsing

CVE-2026-102769EUVD-2026-131643Published , updated

6.8MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2.26.35.74
Who is exposed
Not reported

Summary

WhatsApp for Android and WhatsApp Business for Android have a SQL injection flaw. An attacker can trigger it over the network by sending a specially crafted "order details" message from an unofficial client, and it takes effect when the recipient taps the message. The attacker could delete locally stored WhatsApp files and, if the user is online when the message arrives, leak one bit of information about the user's chat database through a timing side channel.

Written by a model

Original description

A SQL injection vulnerability when the recipient tapped on a specially crafted “order details” message from an unofficial client in WhatsApp for Android prior to version 2.26.35.74 could have allowed deletion of locally-stored WhatsApp files and, only if the user is online at time of receipt, leaked one bit of information asked by the attacker about the user’s chat database via an induced-crash delivery receipt timing sidechannel. We have not seen evidence of exploitation in the wild.

What to do

Upgrade to a fixed version: 2.26.35.74.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-102769 (A SQL injection vulnerability when the recipient tapped on a specially crafted “order details” message from an unofficial client in…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-102769 (entry last updated 2026-11-20):
Affected:
- Facebook WhatsApp Business for Android: from 2.22.3.7, fixed in 2.26.35.74
- Facebook WhatsApp for Android: from 2.22.3.7, fixed in 2.26.35.74
Fixed versions: 2.26.35.74.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-102769 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-102769 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.facebook.com/security/advisories/cve-2026-102769
- https://www.whatsapp.com/security/advisories/2026
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-102769
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-102769"}.

Affected versions

cve.now Index

10Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.8/10CVSS 6.8
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. cve.now early warning

    WhatsApp fixes Android flaw CVE-2026-23871 that it believes a scammer used

  3. First seen by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  5. Record last updated

Evidence 4

KindSource
Vendor advisory 2Establishes: Affected and fixed versions.
Linkfacebook.com · security/advisories/cve-2026-102769
Linkwhatsapp.com · security/advisories/2026
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-102769
RecordNVD · CVE-2026-102769

Questions about CVE-2026-102769

Is CVE-2026-102769 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-102769?

WhatsApp Business for Android: from 2.22.3.7 before 2.26.35.74. WhatsApp for Android: from 2.22.3.7 before 2.26.35.74.

Source: cve.now feed data

How do I fix CVE-2026-102769?

Upgrade to a fixed version: 2.26.35.74.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.