{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-65092 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-65092 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-65092 is a medium-severity memory corruption vulnerability in espressif esp-idf, published on 21 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-65092 and fix it if it is affected.\n\nWhat it is: CVE-2025-65092 is a medium-severity memory corruption vulnerability in espressif esp-idf, published on 21 Nov 2025. 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-2025-65092 in the wild and no public exploit code.\n\nAffected product: espressif esp-idf. 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-65092/ (Markdown: https://insights.sbomify.com/CVE-2025-65092/index.md)","id":"CVE-2025-65092","markdown":"https://insights.sbomify.com/CVE-2025-65092/index.md","name":"CVE-2025-65092","record":{"aliases":["GHSA-vcw6-jc3p-4gj8"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"ESP32-P4 JPEG decoder","requires_auth":"none","summary":"A malicious JPEG image can trigger an out-of-bounds array access in the ESP32-P4 hardware JPEG decoder, potentially causing crashes or code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-191","name":"Integer Underflow (Wrap or Wraparound)"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. In versions 5.5.1, 5.4.3, and 5.3.4, when the ESP32-P4 uses its hardware JPEG decoder, the software parser lacks necessary validation checks. A specially crafted (malicious) JPEG image could exploit the parsing routine and trigger an out-of-bounds array access. This issue has been fixed in versions 5.5.2, 5.4.4, and 5.3.5. At time of publication versions 5.5.2, 5.4.4, and 5.3.5 have not been released but are fixed respectively in commits 4b8f585, c79cb4d, and 34e2726.","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":"ESP32-P4 JPEG Decoder Header Parsing Vulnerability","id":"CVE-2025-65092","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"LibreNMS is vulnerable to SQL Injection (Boolean-Based Blind) in hostname parameter in ajax_output.php endpoint","id":"CVE-2025-65093"},"packages":[],"prev":{"headline":"XWiki Full Calendar Macro vulnerable to SQL injection through Calendar.JSONService","id":"CVE-2025-65091"},"products":["esp-idf"],"published":"2025-11-21","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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-21","vendors":["espressif"]},"summary":"A malicious JPEG image can trigger an out-of-bounds array access in the ESP32-P4 hardware JPEG decoder, potentially causing crashes or code execution.","url":"https://insights.sbomify.com/CVE-2025-65092/"}