Threat Intelligence / CVE / CVE-2026-22107

CVE-2026-22107 — Google Android

CVSS v3.1 8.4 (HIGH) · EPSS 56.7% (higher than 95.4% of all scored CVEs) · Priority 8/10 · Published 2026-02-20

As of 2026-03-05, CVE-2026-22107 is a HIGH-severity vulnerability in Google Android, CVSS v3.1 8.4, EPSS 56.7% (95.4th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-22107, most recently “Android Exploit Chain — Saito Tech Commercial Spyware: ART Runtime RCE, Binder UAF LPE, Pixel Bootloader Persistence (CVE-2026-22104, CVE-2026-22107, CVE-2026-22112)”.

Last updated: 2026-03-05

What is CVE-2026-22107?

A use-after-free vulnerability exists in the Android binder IPC driver (drivers/android/binder.c) in the transaction buffer release path. Improper reference counting during binder_thread cleanup leads to a dangling pointer to a freed binder_transaction object. An attacker with application-level code execution can exploit this via cross-cache memory reallocation techniques to reclaim the freed object with a controlled kernel structure, obtaining arbitrary kernel read/write primitives. Successful exploitation escalates privileges from application context to kernel, enabling SELinux bypass, credential structure modification, and full root access. The vulnerability affects GKI kernel versions 5.10, 5.15, and 6.1 used across Android 12 through 15. Google TAG identified this as Stage 2 of the Saito Tech (Candiru) commercial spyware exploit chain, chained after CVE-2026-22104 for privilege escalation.

The record classifies CVE-2026-22107 under weakness class CWE-416. Its CVSS v3 base vector states that the flaw requires local access to the host, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality, integrity. 5 affected-product entries are recorded, across 1 vendor, listed below. The identifier was first published 205 days ago.

Severity and exploitation probability

CVSS v3.1 base score
8.4 — HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
EPSS (FIRST)
56.7% probability of exploitation in the next 30 days, higher than 95.4% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
8/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-02-20, last modified 2026-03-05

Is CVE-2026-22107 being exploited?

It currently carries a trending score of 29 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-22107

The record marks a vendor fix as available for CVE-2026-22107. Patch reference: https://source.android.com/docs/security/bulletin/2026/2026-03-01. Vendor advisory: https://source.android.com/docs/security/bulletin/2026/2026-03-01. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-22107

1 tracked threat in the Threadlinqs corpus references CVE-2026-22107, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Seeded from nvd and not yet processed by the Threadlinqs enrichment pipeline, so blank CVSS, EPSS or KEV fields above mean NOT MEASURED rather than measured-absent.

Full detection coverage & IOCs for threats exploiting CVE-2026-22107 are available via the Threadlinqs MCP server (Purple tier). View plans →

← all vulnerabilities · Markdown version · Threadlinqs Intelligence