{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-77118 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-77118 is a high-severity memory corruption vulnerability in Debian GraphicsMagick, published on 20 Aug 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-77118 and fix it if it is affected.\n\nWhat it is: CVE-2026-77118 is a high-severity memory corruption vulnerability in Debian GraphicsMagick, published on 20 Aug 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: There is no known exploitation of CVE-2026-77118 in the wild and no public exploit code.\n\nAffected product: Debian GraphicsMagick. 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-77118/ (Markdown: https://insights.sbomify.com/CVE-2026-77118/index.md)","id":"CVE-2026-77118","markdown":"https://insights.sbomify.com/CVE-2026-77118/index.md","name":"CVE-2026-77118","record":{"aliases":["DEBIAN-CVE-2026-77118","ECHO-a2fc-1e4e-dfa3","GHSA-qjrj-qxx7-fc4j","OESA-2026-3656","UBUNTU-CVE-2026-77118"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GraphicsMagick image library","requires_auth":"none","summary":"A heap out-of-bounds write in the GraphicsMagick PCD decoder allows attackers to corrupt memory and potentially execute code by processing a crafted image file.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"seal","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"A heap out-of-bounds write exists in the Photo CD (PCD) decoder of GraphicsMagick. In DecodeImage() (coders/pcd.c), the Huffman delta loop advances its output pointer with q++ after every decoded delta and never checks it against the end of the heap-allocated luma/chroma plane buffers. The pointer is repositioned only when a sync marker introduces a new plane/row; between sync markers the run length is bounded solely by the input.\n\nA crafted PCD file that positions the pointer near the end of a plane and then supplies a long run of deltas with no intervening sync therefore walks the pointer past the end of the allocation and writes through it. Processing an untrusted PCD file — for example with gm convert or gm identify, or through any application linked against libGraphicsMagick — can corrupt heap memory beyond the buffers.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Out-of-bounds write in GraphicsMagick PCD decoder","id":"CVE-2026-77118","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets","id":"CVE-2026-77119"},"packages":[],"prev":{"headline":"SHIFT_JISX0213 decoding may hang on crafted input","id":"CVE-2026-77117"},"products":["GraphicsMagick","graphicsmagick"],"published":"2026-08-20","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":"total"},"state":"PUBLISHED","updated":"2026-08-26","vendors":["Debian","Fedora Project","GraphicsMagick Group"]},"summary":"A heap out-of-bounds write in the GraphicsMagick PCD decoder allows attackers to corrupt memory and potentially execute code by processing a crafted image file.","url":"https://insights.sbomify.com/CVE-2026-77118/"}