# CVE-2026-96609: Denial of service in Albatross

> Authorized users can cause a denial of service in Robur Albatross by filling the ring buffer, leading to an infinite loop in the console.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-p97r-9rrc-gr9r, OSEC-2026-09

## What is CVE-2026-96609?

CVE-2026-96609 is a high-severity denial of service vulnerability in Robur Albatross, published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Robur Albatross 1.0.0 through 2.x before 2.7.2 does not limit use of the ring buffer, leading to an albatross-console loop with no recognized termination condition. This is only exploitable by users who can send console subscription commands to unikernels that produce sufficient log output to fill the ring buffer (1024 lines). It is not exploitable by unauthorized clients.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

Upgrade to a fixed version.

## Is CVE-2026-96609 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96609 is a high-severity denial of service vulnerability in Robur Albatross, published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-96609 in the wild and no public exploit code.

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

## Sources

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

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