ChromeWeb browser · Google
CVE-2011-3926
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 · uneditedHeap-based buffer overflow in the tree builder in Google Chrome before 16.0.912.77 allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.
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 · moderate confidenceHeap-based buffer overflow in the tree builder component of Google Chrome (versions prior to 16.0.912.77). The tree builder is likely involved in parsing HTML/XML structures during page rendering. This memory corruption vulnerability could allow attackers to overwrite heap memory, potentially achieving code execution or causing browser crashes.
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
< 16.0.912.77
SafariWeb browser
< 6.0< 10.7< 6.0CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Identify Google Chrome versionCheck the installed Chrome version (typically via Help > About Google Chrome or chrome://version in the address bar)Affected if Installed version is earlier than 16.0.912.77
-
Identify Apple Safari versionCheck the installed Safari version (typically via Safari > About Safari on Mac, or Help > About on Windows)Affected if Installed version is earlier than 6.0
-
Identify Apple iTunes versionCheck the installed iTunes version (typically via Help > About iTunes)Affected if Installed version is earlier than 10.7
-
Identify Apple iPhone OS versionCheck the device iOS version (via Settings > General > About on the iOS device)Affected if Installed iOS version is earlier than 6.0
-
Confirm tree builder is in useThe tree builder is a core HTML/XML parsing component used during page rendering. Any use of the browser to render web content activates this component.Affected if The browser or application is used to render web content while running an affected version
You are affected if any of the following are true: Chrome < 16.0.912.77, Safari < 6.0, iTunes < 10.7, or iPhone OS < 6.0, and the application is used to render web content.
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.
From vendor data6.010.716.0.912.77
Update Google Chrome to version 16.0.912.77 or later. In enterprise environments, deploy the update via patch management systems and verify completion across all managed endpoints.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3926 — 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-2011-3926 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