ChromeWeb browser · Google
CVE-2024-7533
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 · uneditedUse after free in Sharing in Google Chrome on iOS prior to 127.0.6533.99 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
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 confidenceA use-after-free vulnerability in the Sharing component of Google Chrome on iOS allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. The vulnerability exists in versions prior to 127.0.6533.99 and could allow arbitrary code execution or heap corruption.
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
< 127.0.6533.99CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 is installed on iOSOpen the App Library or check the home screen for the Google Chrome icon (red/green circle with white 'C')Affected if Chrome for iOS is present on the device
-
Determine the installed Chrome versionOpen Chrome, tap the three dots menu, go to Settings, then scroll to the bottom where the version number is displayedAffected if The displayed version number is below 127.6533.99
-
Verify the Sharing component is in useThis is a built-in component of Chrome for iOS - the Sharing feature is integrated into the browser and cannot be disabled separatelyAffected if Chrome for iOS is running any version below 127.6533.99, as the vulnerable code exists in the Sharing component regardless of user configuration
The environment is affected if Google Chrome for iOS is installed and its version number is lower than 127.6533.99, since the use-after-free vulnerability exists in the built-in Sharing component of those versions.
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 · scoped127.0.6533.99
Update Google Chrome on iOS to version 127.0.6533.99 or later. Organizations should ensure all managed iOS devices have the latest Chrome version deployed via MDM or users have been instructed to update.
Chrome for iOS version 127.0.6533.99 or later
- Open the App Store on your iOS device
- Search for "Google Chrome" or locate it in your installed applications
- Tap the "Update" button to update Chrome to version 127.0.6533.99 or later
- Alternatively, enable automatic app updates in App Store settings to ensure future security patches are applied automatically
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
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7533 — 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-7533 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