Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Medium severity, with a CVSS score of 6.4, published 26 June 2026.
- Which products and versions are affected?
- nono-py (PyPI) >= 0.9.0, < 0.10.1.
- Is there a fix for This vulnerability?
- A patch was published on 2026-06-26: Fixed in version 0.10.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked with local access, in a software library.
- Am I affected?
- Check whether you run nono-py (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability exists in nono-py's sandboxed_exec() when using CapabilitySet.proxy_only() on Linux kernels older than 6.7 (which lack Landlock ABI v4 support). In these environments, the Python binding fails to correctly install and supervise the seccomp-notify fallback mechanism intended to enforce proxy-only policies. An attacker with code execution within the sandbox can bypass the proxy by unsetting environment variables (HTTP_PROXY/HTTPS_PROXY) or using raw sockets to establish direct TCP connections. This allows the process to reach restricted endpoints, such as the cloud metadata service (169.254.169.254), potentially leaking IAM credentials. The issue is fixed in version 0.10.1.
Affected products
- nolabs-ai nono-py >= 0.9.0, < 0.10.1
Timeline
- 2026-05-23: disclosed
- 2026-06-26: advisory
- 2026-06-26: patched: Fixed in version 0.10.1