Authorization Flaw in nono-cli (CVE-2026-47128)
Summary
Vulnerability in nono-cli (CVE-2026-47128). Data can be tampered with by attackers. Exploitable via make. Mitigation: upgrade to 0.55.0 or later.
Original description
The description as published by the source.
nono is software that allows users to run AI agents in a zero-latency sandbox. Prior to version 0.55.0, 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. Version 0.55.0 patches the issue.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47128 has been found in nono-cli.
Attackers can target a specific entry point like make over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.1/10.
What to do: upgrade nono-cli to 0.55.0 or later.
If unsure, ask your IT team or search "nono-cli CVE-2026-47128" on the vendor's site.
CVE-2026-47128 (nono-cli) — CWE-863 / CVSS v3 6.1
Attack vector: local / no user interaction
Attack surface: make / gcc / opencode / claude
Patched: 0.55.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in nono-cli. Attackers reach the vulnerable code path via make.
Check the vendor advisory for the affected versions of nono-cli. Attack surface: make / gcc / opencode / claude.
Severity: Medium (CVSS 6.1/10). Data can be tampered with by attackers.
Update to 0.55.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'nono-cli' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'nono-cli' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
nono-cliを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade nono-cli to 0.55.0ステージング環境で 0.55.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com