# CVE-2026-102621: Freedesktop Poppler SplashClip.cc clipToPath integer overflow

> A local attacker can trigger an integer overflow in Poppler's SplashClip component, potentially causing a denial of service.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-102621, ECHO-9660-f07b-634e, GHSA-fxmp-c8v9-778f, UBUNTU-CVE-2026-102621

## What is CVE-2026-102621?

CVE-2026-102621 is a medium-severity vulnerability in Freedesktop Poppler, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was identified in Freedesktop Poppler up to 26.08.0. Affected is the function SplashClip::clipToPath of the file splash/SplashClip.cc. Such manipulation leads to integer overflow. The attack can only be performed from a local environment. The exploit is publicly available and might be used. Upgrading to version 26.09.0 is able to address this issue. The name of the patch is 323c91036d99926a8b90dc14329f7b40aece22f8. It is recommended to upgrade the affected component.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-102621 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102621 is a medium-severity vulnerability in Freedesktop Poppler, published on 29 Sep 2026. 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-2026-102621 in the wild and no public exploit code.

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

## Sources

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

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