LiveActive security incident?Get immediate response
CVE Record

CVE-2022-4926: Insufficient policy enforcement in Intents in Google Chrome on Android prior to 109.0.5414.119 allowed a re...

Insufficient policy enforcement in Intents in Google Chrome on Android prior to 109.0.5414.119 allowed a remote attacker to bypass same origin policy via a crafted HTML page. (Chromium security severity: Medium)

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Chrome on Android had a same-origin policy bypass tied to Android Intents. A malicious web page could trigger the flaw if a user interacted with it, with the reported impact focused on integrity rather than data theft or service disruption.

Executive priority

Treat as a routine but time-bound browser update issue. It is not known exploited from the provided sources, but browser same-origin bypasses can affect trust boundaries and should not remain in mobile fleets.

Technical view

CVE-2022-4926 is an insufficient policy enforcement issue in Chrome on Android before 109.0.5414.119. The CVSS vector is network-accessible, low complexity, no privileges, user interaction required, with high integrity impact and no confidentiality or availability impact. Chromium rated it Medium severity.

Likely exposure

Exposure is most relevant for Android devices running Chrome versions before 109.0.5414.119. Managed mobile fleets, BYOD Android users, and browsers pinned to old versions should be checked first.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The described attack requires a crafted HTML page and user interaction, so phishing or web-link delivery would be the plausible context.

Researcher notes

The record states Chrome on Android before 109.0.5414.119, but one provided release reference is a desktop stable-channel post. Validate platform scope against vendor records before broad reporting. The public Chromium bug may have restricted details.

Mitigation direction

  • Update Chrome on Android to 109.0.5414.119 or later where applicable.
  • Enforce browser update compliance through mobile device management.
  • Check Google Chrome release guidance for affected platform details.
  • Review Linux package advisories if maintaining Chromium-derived packages.

Validation and detection

  • Inventory Android Chrome versions across managed and BYOD devices.
  • Flag Chrome on Android versions earlier than 109.0.5414.119.
  • Confirm mobile update policies prevent long-term browser pinning.
  • Monitor the CVE and vendor references for corrected scope details.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-522: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-4926 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2022-4926Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleChrome109.0.5414.119Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-522 · source CWE mapping

Insufficiently Protected Credentials

Insufficiently Protected Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.