{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33019 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-33019 is a high-severity vulnerability in saitoha libsixel, published on 14 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-33019 and fix it if it is affected.\n\nWhat it is: CVE-2026-33019 is a high-severity vulnerability in saitoha libsixel, published on 14 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33019 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-33019/ (Markdown: https://insights.sbomify.com/CVE-2026-33019/index.md)","id":"CVE-2026-33019","markdown":"https://insights.sbomify.com/CVE-2026-33019/index.md","name":"CVE-2026-33019","record":{"aliases":["DEBIAN-CVE-2026-33019","GHSA-c854-ffg9-g72c","UBUNTU-CVE-2026-33019"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SIXEL encoder/decoder library","requires_auth":"none","summary":"An integer overflow in libsixel's img2sixel tool allows attackers to trigger out-of-bounds heap reads via crafted crop arguments, causing crashes or information disclosure.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"libsixel","vendor":"saitoha"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. Versions 1.8.7 and prior contain an integer overflow leading to an out-of-bounds heap read in the --crop option handling of img2sixel, where positive coordinates up to INT_MAX are accepted without overflow-safe bounds checking. In sixel_encoder_do_clip(), the expression clip_w + clip_x overflows to a large negative value when clip_x is INT_MAX, causing the bounds guard to be skipped entirely, and the unclamped coordinate is passed through sixel_frame_clip() to clip(), which computes a source pointer far beyond the image buffer and passes it to memmove(). An attacker supplying a specially crafted crop argument with any valid image can trigger an out-of-bounds read in the heap, resulting in a reliable crash and potential information disclosure. This issue has been fixed in version 1.8.7-r1.","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 leads to Out-of-bounds Read in img2sixel","id":"CVE-2026-33019","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":"libsixel: Integer Overflow in write_png_to_file() leads to Heap-based Buffer Overflow","id":"CVE-2026-33020"},"packages":[],"prev":{"headline":"libsixel: Use-After-Free in load_gif()","id":"CVE-2026-33018"},"products":["libsixel"],"published":"2026-04-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":"partial"},"state":"PUBLISHED","updated":"2026-04-15","vendors":["saitoha"]},"summary":"An integer overflow in libsixel's img2sixel tool allows attackers to trigger out-of-bounds heap reads via crafted crop arguments, causing crashes or information disclosure.","url":"https://insights.sbomify.com/CVE-2026-33019/"}