# CVE-2026-79113: Integer overflow in OpenAPV

> A heap-based buffer overflow in OpenAPV allows attackers to execute arbitrary code or cause denial of service via crafted bitstreams.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-cqc9-4w54-7f36

## What is CVE-2026-79113?

CVE-2026-79113 is a medium-severity vulnerability in aswf OpenAPV, published on 3 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OpenAPV before 1.1.1.0 has a read_bitstream heap-based buffer overflow.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

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

## Is CVE-2026-79113 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79113 is a medium-severity vulnerability in aswf OpenAPV, published on 3 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-79113 exists.

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

## Sources

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

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