nono: Sandbox escape on Linux via D-Bus: systemd-run --user

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.1 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

EPSS

• CVE-2026-47128: 0.13% estimated exploitation activity in the next 30 days; percentile 2.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The nono Landlock/seccomp policies allow access to local Unix domain sockets (concrete and abstract). This allows an easy sandbox escape by talking to the per-user systemd dbus socket. Threat scenario: Running Aider, Claude Code, OpenCode or similar tools with "allow bash" policy so that it can invoke arbitrary host tools like make, gcc, etc. to write code. Reproducer Here, instead of running a tool like opencode or claude one can just invoke systemd-run, but this is something an agent could be tricked into doing: Impact Complete sandbox escape. The unsandboxed sibling process can write anywhere the user can write, spawn arbitrary processes with network access, etc. Maintainer Context This issue allows a process running inside the sandbox to escape confinement by interacting with local user-scoped IPC mechanisms and regain the authority already held by the invoking user or service account. The issue impacts the sandbox’s confinement and blast-radius reduction guarantees for…

Published by the source

28 May 2026, 19:55 UTC

Last modified by the source

28 May 2026, 19:55 UTC

Source last checked

26 Oct 2026, 15:42 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-27vp-2mmc-vmh3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47128

Advisory: nono: Sandbox escape on Linux via D-Bus: `systemd-run --user`
IDs: CVE-2026-47128, GHSA-27vp-2mmc-vmh3
Record: https://patchnext.com/advisories/cve-2026-47128 (revision 1, source checked 26 Oct 2026, 15:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nono-cli 0.55.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io nono-cli: affected < 0.55.0; fixed in 0.55.0

## Suggested inspection (read-only)
- crates.io nono-cli: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nono-cli.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-27vp-2mmc-vmh3 (GitHub-reviewed advisory GHSA-27vp-2mmc-vmh3 lists affected ranges: crates.io nono-cli >=0 <0.55.0)

Commands are suggestions: review each one before running it.