{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-5273 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-5273 is a medium-severity use after free vulnerability in Google Chrome, published on 1 Apr 2026. 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-2026-5273 and fix it if it is affected.\n\nWhat it is: CVE-2026-5273 is a medium-severity use after free vulnerability in Google Chrome, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-5273 in the wild and no public exploit code.\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-2026-5273/ (Markdown: https://insights.sbomify.com/CVE-2026-5273/index.md)","id":"CVE-2026-5273","markdown":"https://insights.sbomify.com/CVE-2026-5273/index.md","name":"CVE-2026-5273","record":{"aliases":["DEBIAN-CVE-2026-5273","GHSA-9qc6-pp76-5928","MINI-m5qh-2ppw-h8qg"],"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 execute arbitrary code inside the sandbox via a crafted HTML page due to a use-after-free flaw in Chrome's CSS 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":6.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"Use after free in CSS in Google Chrome prior to 146.0.7680.178 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Use after free in Chrome","id":"CVE-2026-5273","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:chrome","products":["google:chrome"],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Integer overflow in Chrome","id":"CVE-2026-5274"},"packages":[],"prev":{"headline":"Memory corruption in Chrome","id":"CVE-2026-5272"},"products":["Chrome"],"published":"2026-04-01","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":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-02","vendors":["Google"]},"summary":"A remote attacker can execute arbitrary code inside the sandbox via a crafted HTML page due to a use-after-free flaw in Chrome's CSS engine.","url":"https://insights.sbomify.com/CVE-2026-5273/"}