ChromeWeb browser · Google

CVE-2026-13283

HIGH · 7.5 CVSS v3.1 Published 2026-06-25

Fix available

A fix is available. Upgrade to 149.0.7827.201 or later.

See remediation →

82/100

Remediation priority · High

Remotely reachable No privileges 8 weeks old

Official description

NVD · unedited

Use after free in AdFilter in Google Chrome on Android prior to 149.0.7827.201 allowed a remote attacker who convinced a user to engage in specific UI gestures to execute arbitrary code via a crafted HTML page. (Chromium security severity: High)

Technical summary

dbcve analysis · high confidence

Use-after-free vulnerability in Chrome's AdFilter component on Android devices allows a remote attacker to execute arbitrary code via crafted HTML pages requiring specific user UI gestures. The vulnerability exists in versions prior to 149.0.7827.201.

MitigationUpdate Google Chrome for Android to version 149.0.7827.201 or later to patch the use-after-free vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ChromeWeb browser

Affected:< 149.0.7827.201

CVSS breakdown

From the vector

Attack vector: Network
Complexity: High
Privileges: None
User interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm Google Chrome for Android is installed

Open device Settings > Apps > Google Chrome. If Chrome appears in the app list, the browser is installed.

Affected if Google Chrome for Android is present on the device
Locate the Chrome version number

Open Chrome, tap the three-dot menu > Settings > About Chrome. The version is displayed at the top of the screen.

Affected if Unable to locate version information in About Chrome page
Compare installed version to affected range

Note the version number shown (for example, 149.0.7827.201) and compare it numerically to the threshold 149.0.7827.201. Versions below this threshold (such as 148.x.x.x) are in the affected range.

Affected if Installed version is less than 149.0.7827.201 (for example, 148.0.5359.98 or any 147.x.x.x release)
Verify the AdFilter component context

This vulnerability exists in Chrome's AdFilter component. The flaw is triggered when viewing crafted HTML pages that require specific user interactions (such as tapping). The AdFilter feature is built into Chrome for Android's ad blocking capabilities.

Affected if The vulnerability applies regardless of AdFilter settings, as the flaw exists in the component itself when processing certain HTML content

If Google Chrome for Android version is below 149.0.7827.201, the device is affected by this use-after-free vulnerability in the AdFilter component.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 149.0.7827.201 or later

Fixed in 149.0.7827.201

Interim mitigation

Update Google Chrome for Android to version 149.0.7827.201 or later to patch the use-after-free vulnerability.

Recommended fix High confidence

Chrome Android 149.0.7827.201

Open Google Play Store on your Android device
Search for "Google Chrome" or locate it in your installed apps
Tap "Update" to install Chrome version 149.0.7827.201 or later
Alternatively, ensure Chrome auto-updates are enabled in Play Store settings
After updating, verify the version in Chrome Settings > About Chrome

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing2.0 h
Review / QA1.0 h

9.0 hours of engineering $1,600

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-13283 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

chromereleases.googleblog.comVendor Advisory
issues.chromium.orgPermissions Required
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13283 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-13283?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsUpgrade to 149.0.7827.201 or later

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Chrome

Remediation

A high-priority fix

Fix this in Chrome 9 hrs · Low

Typical engagement from $1,600

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-13283 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References