# CVE-2026-4985: dloebl CGIF GIF Image cgif.c cgif_addframe integer overflow

> An integer overflow in the CGIF library allows remote attackers to cause a denial of service via crafted GIF image dimensions.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** DEBIAN-CVE-2026-4985, GHSA-j9q5-hw2p-xmcf, UBUNTU-CVE-2026-4985

## What is CVE-2026-4985?

CVE-2026-4985 is a medium-severity vulnerability in dloebl CGIF, published on 27 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability was identified in dloebl CGIF up to 0.5.2. This vulnerability affects the function cgif_addframe of the file src/cgif.c of the component GIF Image Handler. The manipulation of the argument width/height leads to integer overflow. The attack may be initiated remotely. The identifier of the patch is b0ba830093f4317a5d1f345715d2fa3cd2dab474. It is suggested to install a patch to address this issue.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-189

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


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

Apply the vendor's patch.

## Is CVE-2026-4985 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4985 is a medium-severity vulnerability in dloebl CGIF, published on 27 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-4985 in the wild and no public exploit code.

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

## Sources

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

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