Skip to content
major vulnerability· requires attention

Remote code execution in Android platform component affects large numbers of devices and enterprise mobile endpoints; widespread impact likely.

Mobile

CVE-2026-49879

8.8
High
EPSS 0.29%Patch availableSep 11, 2026

Android integer overflow enabling remote code execution in rw_t3t component

common questions

Is CVE-2026-49879 being exploited?

Not confirmed. CVE-2026-49879 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.29% probability of exploitation in the next 30 days.

How severe is CVE-2026-49879?

CVE-2026-49879 is rated High with a CVSS score of 8.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-2026-49879?

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

What does CVE-2026-49879 affect?

CVE-2026-49879 affects Android devices (rw_t3t component / NFC subsystem). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-49879?

Apply Android security update to affected devices immediately.

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

executive summary
technical analysis
affected
Android devices (rw_t3t component / NFC subsystem)
impact

Remote code execution via integer overflow/out-of-bounds write; attacker can run arbitrary code without user interaction.

action required

Immediate action required

affected versions
Google Android
  • affected17
  • affected16-qpr2
  • affected16
  • affected15
  • affected14

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free