{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2021-4102 in the wild since at least 15 Dec 2021.","fix":"Upgrade to a fixed version. US federal agencies must fix it by 29 Dec 2021.","what":"CVE-2021-4102 is a high-severity use after free vulnerability in Google Chrome, published on 11 Feb 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-4102 and fix it if it is affected.\n\nWhat it is: CVE-2021-4102 is a high-severity use after free vulnerability in Google Chrome, published on 11 Feb 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: Yes. Attackers have exploited CVE-2021-4102 in the wild since at least 15 Dec 2021.\n\nAffected product: Google Chrome. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-4102/ (Markdown: https://insights.sbomify.com/CVE-2021-4102/index.md)","id":"CVE-2021-4102","markdown":"https://insights.sbomify.com/CVE-2021-4102/index.md","name":"CVE-2021-4102","record":{"aliases":["DEBIAN-CVE-2021-4102","GHSA-vjvx-2q28-pjv2","UBUNTU-CVE-2021-4102"],"analysis":{"component_type":"browser","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Google Chrome","requires_auth":"none","summary":"A remote attacker can exploit heap corruption via a crafted HTML page due to a use-after-free flaw in the V8 engine.","user_interaction":"required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Chrome","cpe":[{"product":"chrome","vendor":"google"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"Use after free in V8 in Google Chrome prior to 96.0.4664.110 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"exploited"},"has_fix":true,"headline":"Google Chromium V8 Use-After-Free","id":"CVE-2021-4102","indexable":true,"kev":{"dateAdded":"2021-12-15","dueDate":"2021-12-29","knownRansomwareCampaignUse":"Unknown","product":"Chromium V8","requiredAction":"Apply updates per vendor instructions.","vendorProject":"Google","vulnerabilityName":"Google Chromium V8 Use-After-Free Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"google:chrome","products":["google:chrome"],"type":"use_after_free","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site Scripting (XSS) - Stored in vanessa219/vditor","id":"CVE-2021-4103"},"packages":[],"prev":{"headline":"Memory corruption in Chrome","id":"CVE-2021-4101"},"products":["Chrome"],"published":"2022-02-11","related":[{"cvss_score":9.6,"headline":"Google Chromium GPU Heap Buffer Overflow","id":"CVE-2022-4135","kev_date_added":"2022-11-28","published":"2022-11-25"},{"cvss_score":9.6,"headline":"Google Chrome Use-After-Free","id":"CVE-2020-16017","kev_date_added":"2021-11-03","published":"2021-01-08"},{"cvss_score":9.6,"headline":"Google Chrome for Android UI Heap Buffer Overflow","id":"CVE-2020-16010","kev_date_added":"2021-11-03","published":"2020-11-03"},{"cvss_score":8.8,"headline":"Google Chromium V8 Out of Bounds Write","id":"CVE-2026-87491","kev_date_added":"2026-09-09","published":"2026-09-09"},{"cvss_score":8.8,"headline":"Google Chromium V8 Type Confusion","id":"CVE-2026-85046","kev_date_added":"2026-09-04","published":"2026-09-03"},{"cvss_score":8.8,"headline":"Google Chromium V8 Out-of-Bounds Read and Write","id":"CVE-2026-11645","kev_date_added":"2026-06-09","published":"2026-06-08"},{"cvss_score":8.8,"headline":"Google Dawn Use-After-Free","id":"CVE-2026-5281","kev_date_added":"2026-04-01","published":"2026-04-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-21","vendors":["Google"]},"summary":"A remote attacker can exploit heap corruption via a crafted HTML page due to a use-after-free flaw in the V8 engine.","url":"https://insights.sbomify.com/CVE-2021-4102/"}