{"answers":{"affected":"4 open source packages ship an affected version, including pillow. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59205 exists.","fix":"Upgrade pillow to 12.3.0 or later.","what":"CVE-2026-59205 is a high-severity memory corruption vulnerability in Python Pillow, published on 14 Jul 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-59205 and fix it if it is affected.\n\nWhat it is: CVE-2026-59205 is a high-severity memory corruption vulnerability in Python Pillow, published on 14 Jul 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-59205 exists.\n\nAffected packages and fixed versions:\n- pillow (Bitnami): affected all versions; fixed in 12.3.0\n- pillow (PyPI): affected all versions; fixed in 12.3.0\n- pillow (PyPI): affected all versions; fixed in 12.3.0\n- pillow (PyPI): affected all versions; fixed in 12.3.0\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-59205/ (Markdown: https://insights.sbomify.com/CVE-2026-59205/index.md)","id":"CVE-2026-59205","markdown":"https://insights.sbomify.com/CVE-2026-59205/index.md","name":"CVE-2026-59205","record":{"aliases":["BIT-pillow-2026-59205","DEBIAN-CVE-2026-59205","ECHO-dd51-3327-b7ce","GHSA-9hw9-ch79-4vh6","MINI-2x3j-5qpj-r6rq","MINI-3vjv-6873-wprc","MINI-4x76-pxqc-jh76","MINI-63x2-g86r-jpgj","MINI-75w5-m3qp-wv3r","MINI-966g-v7xc-xhg5","MINI-967p-wjvq-3fjw","MINI-pmg9-v6pv-h82p","MINI-xm6h-vv65-pv7r","MINI-xppc-6f85-7rfp","MINI-xwgv-fv9w-45q9","PYSEC-2026-3453","ROOT-APP-PYPI-CVE-2026-59205","UBUNTU-CVE-2026-59205"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Python imaging library","requires_auth":"none","summary":"Attackers can trigger heap corruption in Pillow via mismatched image modes, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pillow","vendor":"python"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Pillow is a Python imaging library. Prior to 12.3.0, Pillow's ImageCms.ImageCmsTransform.apply(im, imOut) API can trigger controlled native heap corruption when the caller supplies an output image whose mode does not match the transform's declared output mode. This issue is fixed in version 12.3.0.","ecosystems":["Bitnami","PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Pillow: Controlled heap out-of-bounds write in `ImageCmsTransform.apply()` via output mode mismatch","id":"CVE-2026-59205","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"python:pillow","products":["python:pillow"],"type":"memory_corruption","year":"2026"},"n_packages":4,"n_references":4,"next":{"headline":"n8n: Prototype Pollution via Workflow Credentials Leads to Unauthenticated User and Project Enumeration","id":"CVE-2026-59206"},"packages":[{"ecosystem":"Bitnami","fixed":["12.3.0"],"introduced":["0"],"last_affected":[],"package":"pillow","purl":"pkg:bitnami/pillow","source":"BIT-pillow-2026-59205"},{"ecosystem":"PyPI","fixed":["12.3.0"],"introduced":["0"],"last_affected":[],"package":"pillow","purl":null,"source":"GHSA-9hw9-ch79-4vh6"},{"ecosystem":"PyPI","fixed":["12.3.0"],"introduced":["0"],"last_affected":[],"package":"pillow","purl":"pkg:pypi/pillow","source":"GHSA-9hw9-ch79-4vh6"},{"ecosystem":"PyPI","fixed":["12.3.0"],"introduced":["0"],"last_affected":[],"package":"pillow","purl":"pkg:pypi/pillow","source":"PYSEC-2026-3453"}],"prev":{"headline":"Pillow JPEG2000 tiled decode retains a growing scratch buffer and can be used for denial of service","id":"CVE-2026-59204"},"products":["Pillow"],"published":"2026-07-14","related":[{"cvss_score":10,"headline":"Pillow command injection","id":"CVE-2014-3007","kev_date_added":null,"published":"2014-04-27"},{"cvss_score":9.8,"headline":"Pillow multi-frame loaders can reuse stale native image storage after mode transitions","id":"CVE-2026-96639","kev_date_added":null,"published":"2026-10-21"},{"cvss_score":9.8,"headline":"Buffer over-flow in Pillow","id":"CVE-2022-30595","kev_date_added":null,"published":"2022-05-25"},{"cvss_score":9.8,"headline":"Out of bounds write in Pillow","id":"CVE-2021-25289","kev_date_added":null,"published":"2021-03-19"},{"cvss_score":9.8,"headline":"Pillow Integer overflow in ImagingResampleHorizontal","id":"CVE-2016-4009","kev_date_added":null,"published":"2016-04-13"},{"cvss_score":9.2,"headline":"Pillow: Heap buffer overflow in _tiffWriteProc when saving TIFF to BytesIO","id":"CVE-2026-112393","kev_date_added":null,"published":"2026-10-19"},{"cvss_score":9.2,"headline":"Pillow: Heap buffer overflow in FlashPix (FPX) JPEG decoding leads to code execution","id":"CVE-2026-112398","kev_date_added":null,"published":"2026-10-19"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["python-pillow"]},"summary":"Attackers can trigger heap corruption in Pillow via mismatched image modes, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2026-59205/"}