{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-34961 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-34961 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34961 is a medium-severity memory corruption vulnerability in barebox, published on 11 May 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34961 and fix it if it is affected.\n\nWhat it is: CVE-2026-34961 is a medium-severity memory corruption vulnerability in barebox, published on 11 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-34961 in the wild and no public exploit code.\n\nAffected product: barebox. 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-34961/ (Markdown: https://insights.sbomify.com/CVE-2026-34961/index.md)","id":"CVE-2026-34961","markdown":"https://insights.sbomify.com/CVE-2026-34961/index.md","name":"CVE-2026-34961","record":{"aliases":["GHSA-vv9w-vff6-5rx9"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"barebox bootloader","requires_auth":"none","summary":"Attackers can trigger heap out-of-bounds reads in barebox via malicious ext4 images, potentially leaking memory or causing crashes during boot.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"barebox","vendor":"pengutronix"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"barebox prior to version 2026.04.0 contains out-of-bounds read vulnerabilities in ext4 extent parsing due to missing validation of the eh_entries field against buffer capacity in fs/ext4/ext4_common.c. Attackers can supply a malicious ext4 filesystem image via USB, SD card, or network boot to trigger heap out-of-bounds reads during boot-time filesystem parsing, potentially redirecting reads to arbitrary disk offsets.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"barebox ext4 Extent Parsing Out-of-Bounds Read","id":"CVE-2026-34961","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"barebox ext4 Directory Parsing Infinite Loop Denial of Service","id":"CVE-2026-34962"},"packages":[],"prev":{"headline":"barebox Out-of-Bounds Read in DHCP Option Parsing","id":"CVE-2026-34960"},"products":["barebox"],"published":"2026-05-11","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-15937","kev_date_added":null,"published":"2019-09-05"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-15938","kev_date_added":null,"published":"2019-09-05"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2020-13910","kev_date_added":null,"published":"2020-06-07"},{"cvss_score":8.6,"headline":"barebox EFI PE Loader Memory Safety Vulnerabilities","id":"CVE-2026-34963","kev_date_added":null,"published":"2026-05-11"},{"cvss_score":8.3,"headline":"barebox: FIT Signature Verification Bypass Vulnerability","id":"CVE-2026-33243","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2021-37847","kev_date_added":null,"published":"2021-08-02"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2021-37848","kev_date_added":null,"published":"2021-08-02"}],"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":"partial"},"state":"PUBLISHED","updated":"2026-07-18","vendors":["barebox"]},"summary":"Attackers can trigger heap out-of-bounds reads in barebox via malicious ext4 images, potentially leaking memory or causing crashes during boot.","url":"https://insights.sbomify.com/CVE-2026-34961/"}