ChromeWeb browser · Google
CVE-2026-8585
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.
NVD · uneditedInappropriate implementation in Media in Google Chrome on iOS prior to 148.0.7778.168 allowed a remote attacker who had compromised the renderer process to perform an out of bounds memory read via a crafted HTML page. (Chromium security severity: Medium)
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.
dbcve analysis · high confidenceAn out-of-bounds memory read vulnerability in the Media component of Google Chrome on iOS (versions prior to 148.0.7778.168) allows a remote attacker with an already compromised renderer process to read arbitrary memory via a crafted HTML page, potentially leaking sensitive information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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.
NVD · CPE data
ChromeWeb browser
< 148.0.7778.168CVSS 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.
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? 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.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Google Chrome on iOS is installedOpen the iOS Settings app, scroll down to see the list of installed apps, and verify Google Chrome appears in the listAffected if Google Chrome is installed on the iOS device
-
Find the installed Chrome versionOpen Google Chrome, tap the three dots menu (top right), go to Settings, tap Chrome, and view the Version field under 'Chrome version'Affected if The displayed version number is lower than 148.0.7778.168 (e.g., 148.0.7778.100 or earlier)
-
Verify the renderer process could be compromisedThis is an attack prerequisite: the attacker needs a compromised renderer process. In typical use, this occurs if the user visits a malicious website that exploits another vulnerability to compromise the renderer. No direct config check is available for users.Affected if The user has visited untrusted or compromised websites while using Chrome on iOS, which could have triggered the exploit chain
The user is affected if they have Google Chrome on iOS with a version lower than 148.0.7778.168 and have browsed untrusted web pages, as the vulnerability can be triggered via crafted HTML when combined with a compromised renderer process.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped148.0.7778.168
Update Google Chrome on iOS to version 148.0.7778.168 or later to remediate this vulnerability. Organizations should ensure automatic updates are enabled or push the update to managed devices.
Chrome iOS version 148.0.7778.168 or later
- Open the App Store on your iOS device
- Search for Google Chrome in the App Store
- Tap the Update button to update Chrome for iOS to version 148.0.7778.168 or later
- Alternatively, enable automatic updates in iOS Settings > App Store > Automatic Downloads to ensure future security updates are applied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8585 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8585 in production — separate from our analysis above.
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.
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.
- 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