ChromeWeb browser · Google
CVE-2024-2626
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 · uneditedOut of bounds read in Swiftshader in Google Chrome prior to 123.0.6312.58 allowed a remote attacker to perform out of bounds memory access 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 read vulnerability exists in Swiftshader, Google's software rendering library for WebGL and graphics in Chrome. A remote attacker can exploit this by tricking a user into visiting a crafted HTML page, allowing unauthorized memory access outside allocated buffers. This could potentially expose sensitive information from the victim's machine.
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
< 123.0.6312.58
FedoraOperating system
= 38= 39= 40CVSS 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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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.
-
Check installed Google Chrome versionOpen Chrome, go to chrome://settings/help, or run 'google-chrome --version' in terminalAffected if Version is lower than 123.0.6312.58
-
Check Swiftshader package on FedoraRun 'rpm -q swiftshader' or 'dnf list installed swiftshader'Affected if Package is installed on Fedora 38, 39, or 40 without latest security update
-
Determine if software rendering is in useIn Chrome, navigate to chrome://gpu and look for 'SwiftShader' under 'Graphics Feature Status', or check if hardware acceleration is disabled via chrome://settingsAffected if SwiftShader is listed as active for WebGL or software rendering is enabled
You are affected if you run Google Chrome version below 123.0.6312.58 or have an unpatched swiftshader package on Fedora 38-40, and SwiftShader is being used for graphics rendering.
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 · scoped123.0.6312.58
Update Google Chrome to version 123.0.6312.58 or later. In enterprise environments, deploy the update via centralized patch management systems (e.g., Group Policy, SCCM, Intune) and verify successful installation across affected endpoints.
Chrome 123.0.6312.58 or later
- For Chrome Desktop users: Open Chrome, go to Settings > Help > About Google Chrome, and install any available updates to reach version 123.0.6312.58 or later
- For Fedora systems with Chrome installed: Run 'sudo dnf update google-chrome-stable' to apply the security fix
- Verify the installed version by navigating to chrome://version in the browser address bar
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2626 — 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-2024-2626 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