{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-38427 exists.","fix":"No fix has been published for CVE-2026-38427 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-38427 is a high-severity vulnerability in n/a, published on 27 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-38427 and fix it if it is affected.\n\nWhat it is: CVE-2026-38427 is a high-severity vulnerability in n/a, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-38427 exists.\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-38427/ (Markdown: https://insights.sbomify.com/CVE-2026-38427/index.md)","id":"CVE-2026-38427","markdown":"https://insights.sbomify.com/CVE-2026-38427/index.md","name":"CVE-2026-38427","record":{"aliases":["GHSA-cwmx-qwp4-jp5h"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Tasmota firmware","requires_auth":"none","summary":"A remote attacker can trigger a heap buffer overflow in Tasmota firmware via integer overflow in JPEG processing, potentially leading to code execution or denial of service.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.3,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"An issue in fetch_jpg() in xdrv_10_scripter.ino in Tasmota through 15.3.0.3 allows a remote attacker to cause heap buffer overflow. The Content-Length from a JPEG stream is stored in a uint16_t variable; values above 65535 wrap around, causing allocation of a smaller buffer than the data actually read.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-05-25","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-05-25T10:10:18Z","kind":"github_poc","ref":"https://github.com/sermikr0/CVE-2026-38427","stars":0,"title":"CVE-2026-38427 — Integer Wraparound → Heap Buffer Overflow in Tasmota fetch_jpg() uint16_t (Tasmota \u003c= 15.3.0.3)"}],"tier":"weaponised"},"has_fix":null,"headline":"Integer overflow in n/a","id":"CVE-2026-38427","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in n/a","id":"CVE-2026-38428"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2026-38426"},"products":["n/a"],"published":"2026-05-27","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-27","vendors":["n/a"]},"summary":"A remote attacker can trigger a heap buffer overflow in Tasmota firmware via integer overflow in JPEG processing, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2026-38427/"}