{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-37532 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-37532 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-37532 is a high-severity memory corruption vulnerability in n/a, published on 1 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-37532 and fix it if it is affected.\n\nWhat it is: CVE-2026-37532 is a high-severity memory corruption vulnerability in n/a, published on 1 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-37532 in the wild and no public exploit code.\n\nAffected product: n/a. 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-37532/ (Markdown: https://insights.sbomify.com/CVE-2026-37532/index.md)","id":"CVE-2026-37532","markdown":"https://insights.sbomify.com/CVE-2026-37532/index.md","name":"CVE-2026-37532","record":{"aliases":["GHSA-h5cx-4fh7-xq44"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"CAN low-level service","requires_auth":"none","summary":"A heap buffer over-read in the isotp-c library allows attackers to read out-of-bounds memory or cause crashes via crafted CAN frames.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"automotive_grade_linux","vendor":"linuxfoundation"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AC:L/AV:A/A:H/C:L/I:N/PR:N/S:U/UI:N","version":"3.1"},"cwes":[{"id":"CWE-126","name":"Buffer Over-read"}],"description":"AGL agl-service-can-low-level thru 17.1.12 contains a heap buffer over-read in the isotp-c library. In isotp_continue_receive (receive.c:87-89), the payload_length for a Single Frame is extracted from a 4-bit nibble in the CAN frame data, yielding values 0-15. However, a standard CAN frame is only 8 bytes, with payload starting at data[1] (7 bytes available). When payload_length exceeds the available data (e.g., nibble=15 but only 7 payload bytes exist), memcpy(message.payload, \u0026data[1], payload_length) reads up to 8 bytes past the end of the data buffer.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2026-37532","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Integer overflow in n/a","id":"CVE-2026-37534"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2026-37531"},"products":["n/a"],"published":"2026-05-01","related":[{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2026-37531","kev_date_added":null,"published":"2026-05-01"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2026-37525","kev_date_added":null,"published":"2026-05-01"},{"cvss_score":7.8,"headline":"Missing authorization in n/a","id":"CVE-2026-37526","kev_date_added":null,"published":"2026-05-01"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2026-37530","kev_date_added":null,"published":"2026-05-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":"partial"},"state":"PUBLISHED","updated":"2026-05-01","vendors":["n/a"]},"summary":"A heap buffer over-read in the isotp-c library allows attackers to read out-of-bounds memory or cause crashes via crafted CAN frames.","url":"https://insights.sbomify.com/CVE-2026-37532/"}