{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44636 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-44636 is a high-severity vulnerability in saitoha libsixel, published on 14 May 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-44636 and fix it if it is affected.\n\nWhat it is: CVE-2026-44636 is a high-severity vulnerability in saitoha libsixel, published on 14 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44636 exists.\n\nAffected product: saitoha libsixel. 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-44636/ (Markdown: https://insights.sbomify.com/CVE-2026-44636/index.md)","id":"CVE-2026-44636","markdown":"https://insights.sbomify.com/CVE-2026-44636/index.md","name":"CVE-2026-44636","record":{"aliases":["DEBIAN-CVE-2026-44636","GHSA-hx93-w8p2-ffh5","UBUNTU-CVE-2026-44636"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SIXEL image library","requires_auth":"none","summary":"An integer overflow in libsixel's encoder allows heap buffer overflows when processing large image dimensions, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"libsixel","vendor":"saitoha"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. From  to 1.8.7-r1, signed integer overflow in sixel_encode_highcolor's allocation size calculation can lead to a heap buffer overflow. The public sixel_encode entry point validates only that width and height are greater than zero, with no upper bound. width and height are multiplied as plain int when computing the allocation size for paletted_pixels and normalized_pixels. Any caller that asks libsixel to encode a pixel buffer with width times height greater than INT_MAX (about 2.15 billion) will hit a wrapped allocation size; under the right wrap, the malloc succeeds with a buffer much smaller than the encoder expects, and the encoder writes past the end of the heap allocation. This vulnerability is fixed in 1.8.7-r2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"libsixel: integer overflow in encoder","id":"CVE-2026-44636","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"libsixel: integer overflow in parser","id":"CVE-2026-44637"},"packages":[],"prev":{"headline":"Kysely: JSON-path traversal injection via unsanitized path-leg metacharacters in `JSONPathBuilder.key()` / `.at()`","id":"CVE-2026-44635"},"products":["libsixel"],"published":"2026-05-14","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-19635","kev_date_added":null,"published":"2019-12-08"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2019-19636","kev_date_added":null,"published":"2019-12-08"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2019-19637","kev_date_added":null,"published":"2019-12-08"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2019-19638","kev_date_added":null,"published":"2019-12-08"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2022-27044","kev_date_added":null,"published":"2022-04-08"},{"cvss_score":8.8,"headline":"Use after free in n/a","id":"CVE-2022-27046","kev_date_added":null,"published":"2022-04-08"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2020-21547","kev_date_added":null,"published":"2021-09-17"}],"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-16","vendors":["saitoha"]},"summary":"An integer overflow in libsixel's encoder allows heap buffer overflows when processing large image dimensions, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2026-44636/"}