{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-37530 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-37530 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-37530 is a high-severity memory corruption vulnerability in n/a, published on 1 May 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-37530 and fix it if it is affected.\n\nWhat it is: CVE-2026-37530 is a high-severity memory corruption vulnerability in n/a, published on 1 May 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-37530 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-37530/ (Markdown: https://insights.sbomify.com/CVE-2026-37530/index.md)","id":"CVE-2026-37530","markdown":"https://insights.sbomify.com/CVE-2026-37530/index.md","name":"CVE-2026-37530","record":{"aliases":["GHSA-grgw-7h7j-hjqm"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Automotive CAN service","requires_auth":"none","summary":"Stack buffer overflow in AGL CAN service allows remote code execution on automotive ECUs via crafted diagnostic requests.","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.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"AGL agl-service-can-low-level thru 17.1.12 contains a stack buffer overflow in the uds-c library. The send_diagnostic_request function in uds.c allocates a 6-byte stack buffer (MAX_DIAGNOSTIC_PAYLOAD_SIZE=6) but copies up to 7 bytes (MAX_UDS_REQUEST_PAYLOAD_LENGTH=7) via memcpy at an offset of 1+pid_length (2-3 bytes), resulting in 1-4 bytes of controlled stack overflow. The payload_length field (uint8_t) has no bounds check against the destination buffer. On 32-bit ARM automotive ECUs without stack canaries, this can lead to return address overwrite and RCE.","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-37530","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":"Path traversal in n/a","id":"CVE-2026-37531"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2026-37526"},"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.1,"headline":"Memory corruption in n/a","id":"CVE-2026-37532","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-01","vendors":["n/a"]},"summary":"Stack buffer overflow in AGL CAN service allows remote code execution on automotive ECUs via crafted diagnostic requests.","url":"https://insights.sbomify.com/CVE-2026-37530/"}