{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2019-5825 in the wild since at least 8 Jun 2022.","fix":"Upgrade to a fixed version. US federal agencies must fix it by 22 Jun 2022.","what":"CVE-2019-5825 is a medium-severity memory corruption vulnerability in Google Chrome, published on 25 Nov 2019. 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-2019-5825 and fix it if it is affected.\n\nWhat it is: CVE-2019-5825 is a medium-severity memory corruption vulnerability in Google Chrome, published on 25 Nov 2019. 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-2019-5825 in the wild since at least 8 Jun 2022.\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-2019-5825/ (Markdown: https://insights.sbomify.com/CVE-2019-5825/index.md)","id":"CVE-2019-5825","markdown":"https://insights.sbomify.com/CVE-2019-5825/index.md","name":"CVE-2019-5825","record":{"aliases":["DEBIAN-CVE-2019-5825","GHSA-3xc7-8f3r-h948","UBUNTU-CVE-2019-5825"],"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":"Remote attackers can execute arbitrary code via heap corruption in Google Chrome by tricking users into visiting a crafted HTML page.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Chrome","cpe":[{"product":"chrome","vendor":"google"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Out of bounds write in JavaScript in Google Chrome prior to 73.0.3683.86 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2019-03-07","github_poc":1,"max_poc_stars":7,"metasploit":1,"nuclei":0,"refs":[{"date":"2019-11-23T11:35:34Z","kind":"github_poc","ref":"https://github.com/timwr/CVE-2019-5825","stars":7,"title":null},{"date":"2019-03-07","kind":"metasploit","ref":"exploit/multi/browser/chrome_array_map","stars":null,"title":"Google Chrome 72 and 73 Array.map exploit"},{"date":"2020-03-09","kind":"exploitdb","ref":"48183","stars":null,"title":"Google Chrome 72 and 73 - Array.map Out-of-Bounds Write (Metasploit)"}],"tier":"exploited"},"has_fix":true,"headline":"Google Chromium V8 Out-of-Bounds Write","id":"CVE-2019-5825","indexable":true,"kev":{"dateAdded":"2022-06-08","dueDate":"2022-06-22","knownRansomwareCampaignUse":"Unknown","product":"Chromium V8","requiredAction":"Apply updates per vendor instructions.","vendorProject":"Google","vulnerabilityName":"Google Chromium V8 Out-of-Bounds Write Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"google:chrome","products":["google:chrome"],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Use after free in Chrome","id":"CVE-2019-5826"},"packages":[],"prev":{"headline":"Memory corruption in Chrome","id":"CVE-2019-5824"},"products":["Chrome"],"published":"2019-11-25","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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"active","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-21","vendors":["Google"]},"summary":"Remote attackers can execute arbitrary code via heap corruption in Google Chrome by tricking users into visiting a crafted HTML page.","url":"https://insights.sbomify.com/CVE-2019-5825/"}