{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-68622 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-68622 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-68622 is a medium-severity memory corruption vulnerability in espressif esp-usb, published on 12 Jan 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-2025-68622 and fix it if it is affected.\n\nWhat it is: CVE-2025-68622 is a medium-severity memory corruption vulnerability in espressif esp-usb, published on 12 Jan 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-2025-68622 in the wild and no public exploit code.\n\nAffected product: espressif esp-usb. 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-2025-68622/ (Markdown: https://insights.sbomify.com/CVE-2025-68622/index.md)","id":"CVE-2025-68622","markdown":"https://insights.sbomify.com/CVE-2025-68622/index.md","name":"CVE-2025-68622","record":{"aliases":["GHSA-g65h-9ggq-9827"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"ESP-IDF USB Host","requires_auth":"none","summary":"A malicious USB device can trigger a stack buffer overflow in the ESP-IDF UVC driver when descriptor printing is enabled, potentially allowing code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"usb_host_uvc_class_driver","vendor":"espressif"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"Espressif ESP-IDF USB Host UVC Class Driver allows video streaming from USB cameras. Prior to 2.4.0, a vulnerability in the esp-usb UVC host implementation allows a malicious USB Video Class (UVC) device to trigger a stack buffer overflow during configuration-descriptor parsing. When UVC configuration-descriptor printing is enabled, the host prints detailed descriptor information provided by the connected USB device. A specially crafted UVC descriptor may advertise an excessively large length. Because this value is not validated before being copied into a fixed-size stack buffer, an attacker can overflow the buffer and corrupt memory. This vulnerability is fixed in 2.4.0.","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":"Espressif ESP-IDF USB Host UVC Class Driver has a stack buffer overflow in UVC descriptor printing","id":"CVE-2025-68622","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2025-68623"},"packages":[],"prev":{"headline":"Trilium Notes has a Timing Attack Vulnerability in /api/login/sync","id":"CVE-2025-68621"},"products":["esp-usb"],"published":"2026-01-12","related":[],"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":"total"},"state":"PUBLISHED","updated":"2026-01-12","vendors":["espressif"]},"summary":"A malicious USB device can trigger a stack buffer overflow in the ESP-IDF UVC driver when descriptor printing is enabled, potentially allowing code execution.","url":"https://insights.sbomify.com/CVE-2025-68622/"}