# CVE-2026-15811: Kronosnet: kronosnet: encryption key exposure in memory after cryptographic configuration changes

> Local attackers can retrieve encryption keys from memory to decrypt cluster traffic or disrupt high-availability clusters in Red Hat Enterprise Linux.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jul 2026
- **Updated:** 21 Aug 2026
- **Also known as:** AZL-93090, DEBIAN-CVE-2026-15811, GHSA-3p9p-8j59-v9h3, UBUNTU-CVE-2026-15811

## What is CVE-2026-15811?

CVE-2026-15811 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in kronosnet's (version <=1.34) cryptographic configuration management. The framework does not correctly zero-out or wipe sensitive memory segments after executing changes to its cryptographic configuration. This omission leaves raw encryption keys resident in memory after the associated structures are freed. A local attacker capable of leveraging memory disclosure techniques could exploit this flaw to retrieve the active encryption key, allowing them to decrypt cluster network communications or inject malicious packets to cause severe high-availability cluster instability.

Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer)

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


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

Apply the vendor's patch.

## Is CVE-2026-15811 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15811 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15811 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-15811/ (Markdown: https://insights.sbomify.com/CVE-2026-15811/index.md)
```

## Sources

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

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