GHSA-72w7-mf9g-733p: Nono py Nono-py Has Proxy-only Network Fallback Vulnerability

MODERATE
CVSS 6.4
CWE-693
Published
Advisory Summary

GHSA-72w7-mf9g-733p is a MODERATE (CVSS 6.4) nono-py has proxy-only network fallback vulnerability (CWE-693: Protection Mechanism Failure) affecting Nono py libraries in the PyPI ecosystem. The issue involves nono-py has proxy-only network fallback bypass on older linux kernels. Remediation is available by upgrading affected packages to version 0.10.1.

GHSA-72w7-mf9g-733p at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-72w7-mf9g-733p
Severity MODERATE
CVSS v3.1 Base Score 6.4
CWE Classification CWE-693: Protection Mechanism Failure
Affected Product Nono py
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 6.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N).

Attack Vector Local (AV:L)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity Low (I:L)
Availability None (A:N)

How to Fix GHSA-72w7-mf9g-733p

To remediate this vulnerability, upgrade all affected Nono py dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

nono-py fixed: 0.10.1
pip install nono-py>=0.10.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show nono-py

How to Check if You Are Affected

To determine whether your Python environment is affected by GHSA-72w7-mf9g-733p, inspect your installed packages using pip:

pip show nono-py

Analyze the terminal output to locate any version of Nono py in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.10.1), your application is affected.

Note: The pip show nono-py command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-693: Protection Mechanism Failure, where the product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. In Nono py, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary On Linux kernels that do not support Landlock network rules, `nono_py.sandboxed_exec()` could run `CapabilitySet.proxy_only(proxy)` without supervising the seccomp-notify proxy-only fallback returned by the Rust core. In that configuration, a sandboxed child process could remove `HTTP_PROXY` / `HTTPS_PROXY` environment variables or use raw sockets and then open direct TCP connections that should have been denied by proxy-only policy. The issue affects proxy-only enforcement. It does not mean that all nono-py network blocking is ineffective. ECS validation showed `caps.block_network()` denied regular TCP and ECS metadata TCP on the tested Linux 6.1 host. ## Impact The intended `proxy_only()` security property is: - child processes may connect only to the local nono proxy port - the proxy enforces host allowlists and metadata/link-local denial - direct TCP to any other target is denied Before the fix, on kernels without Landlock `AccessNet`, the Python binding applied the sandbox and then executed the child, but did not install and supervise the proxy-only seccomp-notify fallback. A child could therefore bypass the proxy layer in that old-kernel path. The highest-impact scenario is a sandboxed workload with access to cloud metadata discovery inputs, where direct TCP to a metadata endpoint could retrieve task or instance credentials after proxy environment variables are removed. ## Affected Conditions The issue requires all of the following: - Linux runtime. - Kernel without Landlock network support, such as Linux 6.1. Landlock network rules require Landlock ABI v4 / Linux 6.7 or newer. - `nono_py.sandboxed_exec()` is used. - The capability set uses `caps.proxy_only(proxy)`. - The child process removes or ignores proxy environment variables, or uses raw sockets. macOS Seatbelt proxy-only enforcement is not affected by this Linux seccomp-notify fallback issue. ## Affected Versions Known affected builds include nono-py versions that expose and use `CapabilitySet.proxy_only()` through `sandboxed_exec()` before the supervised fallback fix in this working tree. Earlier versions that did not expose `CapabilitySet.proxy_only()` are not affected by this specific proxy-only enforcement bug, though they may have separate environment-inheritance risks if callers passed broad parent environment variables into sandboxed children. **CVSS Score Rationale** | Metric | Value | Rationale | |---|---|---| | **Attack Vector (AV)** | L — Local | Exploit is performed by a local process (unsetting env vars or opening raw sockets). Not remotely triggerable. | | **Attack Complexity (AC)** | H — High | All of the following must be true: Linux runtime; kernel < 6.7 (no Landlock ABI v4); `sandboxed_exec()` used; capability set calls `proxy_only()`; child actively bypasses proxy env vars or uses raw sockets. | | **Privileges Required (PR)** | L — Low | Attacker is already executing code inside the sandbox — some user-level privilege is required to get there. | | **User Interaction (UI)** | N — None | No action from a user or operator is needed once the sandboxed child is running. | | **Scope (S)** | C — Changed | The exploit crosses the sandbox security boundary, allowing the child to reach network resources outside the defined policy scope. | | **Confidentiality (C)** | H — High | Highest-impact path: direct TCP to cloud metadata endpoint (169.254.169.254) yields IAM / task credentials. | | **Integrity (I)** | L — Low | Attacker can make arbitrary outbound requests; no direct data modification from the bypass itself, but lateral credential use creates indirect risk. | | **Availability (A)** | N — None | No denial-of-service impact described or implied. | ---

GHSA-72w7-mf9g-733p Affected Nono py Versions

1 component(s)
Fixed Versions:
0.10.1
Product / Package Ecosystem Affected Versions Fixed Version
nono-py
PyPI
≥ 0.9.0
< 0.10.1
0.10.1

References

Frequently Asked Questions

What is GHSA-72w7-mf9g-733p?
GHSA-72w7-mf9g-733p is a security vulnerability in Nono py involving nono-py has proxy-only network fallback bypass on older Linux kernels under CWE-693: Protection Mechanism Failure.
Which Nono py versions are affected?
Affected versions include releases prior to 0.10.1 across affected packages: nono-py.
What version fixes GHSA-72w7-mf9g-733p?
Upgrading to 0.10.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is nono-py affected?
Yes, nono-py is affected in releases prior to 0.10.1. Upgrade your dependency to 0.10.1 or later.
What is the CVSS score of GHSA-72w7-mf9g-733p?
GHSA-72w7-mf9g-733p has a CVSS v3.1 base score of 6.4 (MODERATE) with vector string CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N.
What CWE is associated with GHSA-72w7-mf9g-733p?
GHSA-72w7-mf9g-733p is classified under CWE-693: Protection Mechanism Failure (The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.).
How can I check PyPI dependencies for GHSA-72w7-mf9g-733p?
Run the dependency tree command: 'pip show nono-py'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-72w7-mf9g-733p",
  "modified" : "2026-06-26T20:33:48Z",
  "published" : "2026-06-26T20:33:48Z",
  "aliases" : [ ],
  "summary" : "nono-py has proxy-only network fallback bypass on older Linux kernels",
  "details" : "## Summary\n\nOn Linux kernels that do not support Landlock network rules, `nono_py.sandboxed_exec()` could run `CapabilitySet.proxy_only(proxy)` without supervising the seccomp-notify proxy-only fallback returned by the Rust core.\n\nIn that configuration, a sandboxed child process could remove `HTTP_PROXY` / `HTTPS_PROXY` environment variables or use raw sockets and then open direct TCP connections that should have been denied by proxy-only policy.\n\nThe issue affects proxy-only enforcement. It does not mean that all nono-py network blocking is ineffective. ECS validation showed `caps.block_network()` denied regular TCP and ECS metadata TCP on the tested Linux 6.1 host.\n\n## Impact\n\nThe intended `proxy_only()` security property is:\n\n- child processes may connect only to the local nono proxy port\n- the proxy enforces host allowlists and metadata/link-local denial\n- direct TCP to any other target is denied\n\nBefore the fix, on kernels without Landlock `AccessNet`, the Python binding applied the sandbox and then executed the child, but did not install and supervise the proxy-only seccomp-notify fallback. A child could therefore bypass the proxy layer in that old-kernel path.\n\nThe highest-impact scenario is a sandboxed workload with access to cloud metadata discovery inputs, where direct TCP to a metadata endpoint could retrieve task or instance credentials after proxy environment variables are removed.\n\n## Affected Conditions\n\nThe issue requires all of the following:\n\n- Linux runtime.\n- Kernel without Landlock network support, such as Linux 6.1. Landlock network rules require Landlock ABI v4 / Linux 6.7 or newer.\n- `nono_py.sandboxed_exec()` is used.\n- The capability set uses `caps.proxy_only(proxy)`.\n- The child process removes or ignores proxy environment variables, or uses raw sockets.\n\nmacOS Seatbelt proxy-only enforcement is not affected by this Linux seccomp-notify fallback issue.\n\n## Affected Versions\n\nKnown affected builds include nono-py versions that expose and use `CapabilitySet.proxy_only()` through `sandboxed_exec()` before the supervised fallback fix in this working tree.\n\nEarlier versions that did not expose `CapabilitySet.proxy_only()` are not affected by this specific proxy-only enforcement bug, though they may have separate environment-inheritance risks if callers passed broad parent environment variables into sandboxed children.\n\n\n**CVSS Score Rationale**\n\n| Metric | Value | Rationale |\n|---|---|---|\n| **Attack Vector (AV)** | L — Local | Exploit is performed by a local process (unsetting env vars or opening raw sockets). Not remotely triggerable. |\n| **Attack Complexity (AC)** | H — High | All of the following must be true: Linux runtime; kernel < 6.7 (no Landlock ABI v4); `sandboxed_exec()` used; capability set calls `proxy_only()`; child actively bypasses proxy env vars or uses raw sockets. |\n| **Privileges Required (PR)** | L — Low | Attacker is already executing code inside the sandbox — some user-level privilege is required to get there. |\n| **User Interaction (UI)** | N — None | No action from a user or operator is needed once the sandboxed child is running. |\n| **Scope (S)** | C — Changed | The exploit crosses the sandbox security boundary, allowing the child to reach network resources outside the defined policy scope. |\n| **Confidentiality (C)** | H — High | Highest-impact path: direct TCP to cloud metadata endpoint (169.254.169.254) yields IAM / task credentials. |\n| **Integrity (I)** | L — Low | Attacker can make arbitrary outbound requests; no direct data modification from the bypass itself, but lateral credential use creates indirect risk. |\n| **Availability (A)** | N — None | No denial-of-service impact described or implied. |\n\n---",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "nono-py"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.9.0"
      }, {
        "fixed" : "0.10.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/always-further/nono-py/security/advisories/GHSA-72w7-mf9g-733p"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nolabs-ai/nono-py/commit/3e67dfa11cbe9514f315fdd36473680c318816d7"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/always-further/nono-py"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-693" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-26T20:33:48Z",
    "nvd_published_at" : null
  }
}