# CVE-2026-114596: Integer overflow or wraparound in EPICS Base


- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-4pjg-wpv4-hhf9

## What is CVE-2026-114596?

CVE-2026-114596 is a high-severity vulnerability in The EPICS Community EPICS Base, published on 27 Oct 2026. 

### Official description

In EPICS Base release 7.0.10 and prior, an improper validation of message length values during protocol parsing can trigger an integer overflow, resulting in an out-of-bounds memory write. Successful exploitation can cause process instability or denial of service.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

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

## Is CVE-2026-114596 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114596 is a high-severity vulnerability in The EPICS Community EPICS Base, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114596 in the wild and no public exploit code.

Affected product: The EPICS Community EPICS Base. 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-114596/ (Markdown: https://insights.sbomify.com/CVE-2026-114596/index.md)
```

## Sources

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

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