{"answers":{"affected":"2 open source packages ship an affected version, including electron.","exploited":"There is no known exploitation of CVE-2026-54257 in the wild and no public exploit code.","fix":"Upgrade electron to 42.3.3 or later.","what":"CVE-2026-54257 is a critical memory corruption vulnerability in electron, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54257 and fix it if it is affected.\n\nWhat it is: CVE-2026-54257 is a critical memory corruption vulnerability in electron, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54257 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- electron (npm): affected from 42.3.1; fixed in 42.3.3\n- electron (npm): affected from 42.3.1; fixed in 42.3.3\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-54257/ (Markdown: https://insights.sbomify.com/CVE-2026-54257/index.md)","id":"CVE-2026-54257","markdown":"https://insights.sbomify.com/CVE-2026-54257/index.md","name":"CVE-2026-54257","record":{"aliases":["GHSA-q6m5-f73j-m9mc"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Electron framework","requires_auth":"none","summary":"Incorrect byte length calculations in Electron's Buffer API can cause heap buffer overflows, leading to application crashes or potential code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. From 42.3.1 until 42.3.3, Buffer performs incorrect byte length calculations resulting in heap buffer under/overflow. Most apps will crash and some may perform incorrect buffer allocations in the Node.js Buffer API resulting in unexpected truncation or allocation. This vulnerability is fixed in 42.3.3.","ecosystems":["npm"],"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":"Electron: Buffer performs incorrect byte length calculations resulting in heap buffer under/overflow","id":"CVE-2026-54257","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Cross-monitor event media authorization bypass in direct event media endpoints","id":"CVE-2026-54258"},"packages":[{"ecosystem":"npm","fixed":["42.3.3"],"introduced":["42.3.1"],"last_affected":[],"package":"electron","purl":null,"source":"GHSA-q6m5-f73j-m9mc"},{"ecosystem":"npm","fixed":["42.3.3"],"introduced":["42.3.1"],"last_affected":[],"package":"electron","purl":"pkg:npm/electron","source":"GHSA-q6m5-f73j-m9mc"}],"prev":{"headline":"Winter: Authenticated IDOR in backend FileUpload widget allows cross-user access to attachment metadata","id":"CVE-2026-54256"},"products":["electron"],"published":"2026-06-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-23","vendors":["electron"]},"summary":"Incorrect byte length calculations in Electron's Buffer API can cause heap buffer overflows, leading to application crashes or potential code execution.","url":"https://insights.sbomify.com/CVE-2026-54257/"}