# CVE-2026-116543: Open5GS 1.3.0 through 2.8.0 Heap Out-of-Bounds Write via SBI Multipart Parser


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-25v2-v588-jq8g, GHSA-wvpv-4m2j-8jmq

## What is CVE-2026-116543?

CVE-2026-116543 is a high-severity vulnerability in open5gs, published on 26 Oct 2026. 

### Official description

Open5GS 1.3.0 through 2.8.0 contains a heap out-of-bounds write vulnerability in parse_multipart() that allows unauthenticated attackers to corrupt memory by supplying an empty multipart boundary. Attackers can send a single crafted multipart/related request to the SBI interface of any network function, overflowing the lookbehind buffer and crashing it.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-116543 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116543 is a high-severity vulnerability in open5gs, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116543 in the wild and no public exploit code.

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

## Sources

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

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