# CVE-2026-38076: Integer overflow in n/a

> Attackers can cause a Denial of Service via crafted input due to an integer overflow in the JBIG2 image library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jul 2026
- **Updated:** 14 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-38076, ECHO-4802-3972-57a5, GHSA-v2wp-4h2v-wxcx, OESA-2026-2995, OESA-2026-2996, OESA-2026-3133, OESA-2026-3134, OESA-2026-3135, UBUNTU-CVE-2026-38076

## What is CVE-2026-38076?

CVE-2026-38076 is a high-severity vulnerability in n/a, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An integer overflow in the jbig2_arith_iaid_ctx_new() function of Artifex commit cc37d0 allows attackers to cause a Denial of Service (DoS) via a crafted input.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

Apply the vendor's patch.

## Is CVE-2026-38076 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-38076 is a high-severity vulnerability in n/a, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-38076 in the wild and no public exploit code.

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

## Sources

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

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