# CVE-2026-15813: Kronosnet: kronosnet: memory corruption and out-of-bounds access via malformed network packet defragmentation

> An attacker can cause application crashes or system instability by sending malformed network packets that trigger out-of-bounds memory access in the packet defragmentation engine.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/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:** 20 Jul 2026
- **Updated:** 21 Aug 2026
- **Also known as:** AZL-92898, DEBIAN-CVE-2026-15813, GHSA-32vg-vj46-3h6w, UBUNTU-CVE-2026-15813

## What is CVE-2026-15813?

CVE-2026-15813 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in the network packet de-fragmentation engine of kronosnet (Version affected <= 1.34). The internal reassembly code does not properly validate sequence numbers of incoming payload fragments. An attacker can exploit this lack of verification by transmitting malformed packets with corrupted sequence parameters. Under specific conditions, this forces the packet processing layer to parse data outside the designated bounds of the internal memory structures, causing an out-of-bounds memory access or heap corruption. This behavior can result in sudden application crashes or system instability.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-15813 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15813 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 20 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-15813 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. 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-15813/ (Markdown: https://insights.sbomify.com/CVE-2026-15813/index.md)
```

## Sources

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

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