# CVE-2026-30141: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code via a crafted GIF file due to a buffer overflow in the bitbank2 AnimatedGIF library.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2026
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-vwpr-hw9c-29x5

## What is CVE-2026-30141?

CVE-2026-30141 is a critical memory corruption vulnerability in n/a, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in bitbank2 AnimatedGIF v2.2.0. A buffer overflow in the DecodeLZW function allows remote attackers to cause a denial of service (crash) or potentially execute arbitrary code via a crafted GIF file.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2026-30141?


## How do I fix CVE-2026-30141?

No fix has been published for CVE-2026-30141 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-30141 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30141 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-30141 and fix it if it is affected.

What it is: CVE-2026-30141 is a critical memory corruption vulnerability in n/a, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30141 exists.

Affected product: n/a. 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-2026-30141/ (Markdown: https://insights.sbomify.com/CVE-2026-30141/index.md)
```

## Sources

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

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