# CVE-2025-27796: Memory corruption in GraphicsMagick

> Attackers can trigger out-of-bounds heap memory access via crafted WPG images, potentially leading to code execution or crashes.

- **Severity:** Medium 4.5 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Mar 2025
- **Updated:** 7 Mar 2025
- **Also known as:** DEBIAN-CVE-2025-27796, GHSA-v5xf-gj23-85jx, JLSEC-2026-494, ROOT-OS-ALPINE-322-CVE-2025-27796

## What is CVE-2025-27796?

CVE-2025-27796 is a medium-severity memory corruption vulnerability in Graphicsmagick Graphicsmagick, published on 7 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ReadWPGImage in WPG in GraphicsMagick before 1.3.46 mishandles palette buffer allocation, resulting in out-of-bounds access to heap memory in ReadBlob.

Weakness: CWE-908 (Use of Uninitialized Resource)

## Which versions are affected by CVE-2025-27796?

It affects 1 product.


Products: Graphicsmagick Graphicsmagick.

## How do I fix CVE-2025-27796?

Upgrade to a fixed version.

## Is CVE-2025-27796 being exploited?

There is no known exploitation of CVE-2025-27796 in the wild and no public exploit code.

## Other vulnerabilities in Graphicsmagick Graphicsmagick

- [CVE-2008-6071](https://insights.sbomify.com/CVE-2008-6071/): Memory corruption in n/a (critical 10.0)
- [CVE-2019-11005](https://insights.sbomify.com/CVE-2019-11005/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-11636](https://insights.sbomify.com/CVE-2017-11636/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-11637](https://insights.sbomify.com/CVE-2017-11637/): Null dereference in n/a (critical 9.8)
- [CVE-2017-11641](https://insights.sbomify.com/CVE-2017-11641/): Denial of service in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27796 and fix it if it is affected.

What it is: CVE-2025-27796 is a medium-severity memory corruption vulnerability in Graphicsmagick Graphicsmagick, published on 7 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27796 in the wild and no public exploit code.

Affected product: Graphicsmagick Graphicsmagick. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-27796/ (Markdown: https://insights.sbomify.com/CVE-2025-27796/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-27796
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-27796
- OSV: https://osv.dev/vulnerability/CVE-2025-27796

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-27796/
Summaries are generated and may contain mistakes; the official description above is the record.