# CVE-2026-121517: IrfanView TIFF Wang Annotation heap-based overflow


- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 7 Nov 2026
- **Also known as:** GHSA-99fw-w5ph-h34w

## What is CVE-2026-121517?

CVE-2026-121517 is a low-severity vulnerability in IrfanView, published on 3 Nov 2026. 

### Official description

A vulnerability was detected in IrfanView 4.76.0.0 on Win64. Affected by this vulnerability is an unknown functionality of the component TIFF Wang Annotation Handler. Performing a manipulation results in heap-based buffer overflow. The attack is possible to be carried out remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit is now public and may be used. It is recommended to apply a patch to fix this issue. The vendor confirms: "[T]he TIF-Annotations option is OFF by default. Means, normal users are not affected ... the danger level for this is low".

Weakness: CWE-122 (Heap-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-121517 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121517 is a low-severity vulnerability in IrfanView, published on 3 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121517 exists.

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

## Sources

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

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