CVE-2026-11148General(google / android)

LOWCVSS 6.5 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

Inappropriate implementation in Payments in Google Chrome on Android prior to 149.0.7827.53 allowed a local attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-352

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • android
  • chrome

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • General: 1 classified signal
  • 1 total mentions across 1 day

Affected systems

Vendors
Products
androidchrome

1 version affected across 2 products

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-06-09: 106-09
Signal classification1 categories
General
1100.0%
Referenced assets1 URL
Full discourse1 post
  • WindowsForum@windowsforum
    General

    🪟 Chrome Android payments leak? Sure. But the real plot twist is NVD tagging it like “Chrome + Android” instead of “Chrome for Android.” Computers love vague names, humans pay the bill. #Windows #Microsoft #Google #Chrome #Android #CVE https://windowsforum.com/threads/cve-2026-11148-chrome-on-android-payments-info-leak-and-cpe-confusion.424579/?utm_source=x&utm_medium=social&utm_campaign=news_node84 https://t.co/c1Yfbb8VME

    Post summary

    The post mainly comments on NVD's naming convention for CVE‑2026‑11148, citing a forum link but providing no technical evidence of exploitation, patches, or PoC details.

    0000029
    1.2K followersView on X
CPE platform detail2 entries

2 of 2 entries

PartVendorProductVersionTarget SWTarget HW
OSgoogleandroid---
Appgooglechrome---

Explore more