{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-26399 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-26399 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-26399 is a medium-severity use after free vulnerability in n/a, published on 20 Apr 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-26399 and fix it if it is affected.\n\nWhat it is: CVE-2026-26399 is a medium-severity use after free vulnerability in n/a, published on 20 Apr 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-26399 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-26399/ (Markdown: https://insights.sbomify.com/CVE-2026-26399/index.md)","id":"CVE-2026-26399","markdown":"https://insights.sbomify.com/CVE-2026-26399/index.md","name":"CVE-2026-26399","record":{"aliases":["GHSA-vxch-4r45-jhw9","UBUNTU-CVE-2026-26399"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"STM32 Arduino library","requires_auth":"low_privilege","summary":"A stack-use-after-return in the Arduino_Core_STM32 library allows attackers to cause memory corruption via dangling pointers in timer interrupts.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-562","name":"Return of Stack Variable Address"}],"description":"A stack-use-after-return issue exists in the Arduino_Core_STM32 library prior to version 1.7.0. The pwm_start() function allocates a TIM_HandleTypeDef structure on the stack and passes its address to HAL initialization routines, where it is stored in a global timer handle registry. After the function returns, interrupt service routines may dereference this dangling pointer, resulting in memory corruption.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-04-19","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-04-19T15:49:34Z","kind":"github_poc","ref":"https://github.com/Acen28/CVE-2026-26399-Disclosure","stars":1,"title":null}],"tier":"poc_unverified"},"has_fix":false,"headline":"Use after free in n/a","id":"CVE-2026-26399","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2026-26416"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2026-26396"},"products":["n/a"],"published":"2026-04-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-22","vendors":["n/a"]},"summary":"A stack-use-after-return in the Arduino_Core_STM32 library allows attackers to cause memory corruption via dangling pointers in timer interrupts.","url":"https://insights.sbomify.com/CVE-2026-26399/"}