GHSA-9j7f-3r4p-pwh6: Nono py Nono-py Vulnerable To Authorization Bypass Vulnerability

MODERATE
CVSS 5.2
CWE-1188
Published
Advisory Summary

GHSA-9j7f-3r4p-pwh6 is a MODERATE (CVSS 5.2) nono-py vulnerable to authorization bypass vulnerability (CWE-1188: Initialization of a Resource with an Insecure Default) affecting Nono py libraries in the PyPI ecosystem. The issue involves nono-py vulnerable to authorization bypass / policy confusion. Remediation is available by upgrading affected packages to version 0.11.0.

GHSA-9j7f-3r4p-pwh6 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-9j7f-3r4p-pwh6
Severity MODERATE
CVSS v3.1 Base Score 5.2
CWE Classification CWE-1188: Initialization of a Resource with an Insecure Default
Affected Product Nono py
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 5.2

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

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

How to Fix GHSA-9j7f-3r4p-pwh6

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.11.0
pip install nono-py>=0.11.0
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-9j7f-3r4p-pwh6, 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.11.0), 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-1188: Initialization of a Resource with an Insecure Default, where the product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure. 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

The python API made a restrictive-looking configuration unsafe by default. A caller could configure only reverse- proxy credential routes, put the child in CapabilitySet.proxy_only, and reasonably expect network access to be limited to those routes. Instead, because empty allowed_hosts meant allow-all inside nono-proxy, the child could use the local proxy as a transparent CONNECT tunnel to non-route nominated hosts (not including metadata endpoints). That is an authorization bypass / policy confusion issue: - Intended policy: route-only proxy access. - Actual policy: route-only plus arbitrary transparent CONNECT. - Boundary crossed: sandboxed child gains broader outbound network reach than the Python policy appears to grant. - Impact depends on environment, but it can allow exfiltration or access to unintended internet/internal services through the unsandboxed proxy. This should be classified as medium severity by default, potentially high if users rely on route-only configs for strict egress control around untrusted code or sensitive credentials. The fix is security-relevant because it changes the default from implicit allow-all to explicit opt-in.

GHSA-9j7f-3r4p-pwh6 Affected Nono py Versions

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

References

Frequently Asked Questions

What is GHSA-9j7f-3r4p-pwh6?
GHSA-9j7f-3r4p-pwh6 is a security vulnerability in Nono py involving nono-py vulnerable to authorization bypass / policy confusion under CWE-1188: Initialization of a Resource with an Insecure Default.
Which Nono py versions are affected?
Affected versions include releases prior to 0.11.0 across affected packages: nono-py.
What version fixes GHSA-9j7f-3r4p-pwh6?
Upgrading to 0.11.0 (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.11.0. Upgrade your dependency to 0.11.0 or later.
What is the CVSS score of GHSA-9j7f-3r4p-pwh6?
GHSA-9j7f-3r4p-pwh6 has a CVSS v3.1 base score of 5.2 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N.
What CWE is associated with GHSA-9j7f-3r4p-pwh6?
GHSA-9j7f-3r4p-pwh6 is classified under CWE-1188: Initialization of a Resource with an Insecure Default (The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.).
How can I check PyPI dependencies for GHSA-9j7f-3r4p-pwh6?
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-9j7f-3r4p-pwh6",
  "modified" : "2026-06-26T20:39:43Z",
  "published" : "2026-06-26T20:39:43Z",
  "aliases" : [ ],
  "summary" : "nono-py vulnerable to authorization bypass / policy confusion",
  "details" : "The python API made a restrictive-looking configuration unsafe by default. A caller could configure only reverse-\nproxy credential routes, put the child in CapabilitySet.proxy_only, and reasonably expect network access to be limited\nto those routes. Instead, because empty allowed_hosts meant allow-all inside nono-proxy, the child could use the local\nproxy as a transparent CONNECT tunnel to non-route nominated hosts (not including metadata endpoints).\n\nThat is an authorization bypass / policy confusion issue:\n\n- Intended policy: route-only proxy access.\n- Actual policy: route-only plus arbitrary transparent CONNECT.\n- Boundary crossed: sandboxed child gains broader outbound network reach than the Python policy appears to grant.\n- Impact depends on environment, but it can allow exfiltration or access to unintended internet/internal services\n  through the unsandboxed proxy.\n\nThis should be classified as medium severity by default, potentially high if users rely on route-only configs for strict egress\ncontrol around untrusted code or sensitive credentials. The fix is security-relevant because it changes the default from\nimplicit allow-all to explicit opt-in.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "nono-py"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.11.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.10.1"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/always-further/nono-py/security/advisories/GHSA-9j7f-3r4p-pwh6"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nolabs-ai/nono-py/commit/163fca083a189967b882d1005bfba099fc9a9d63"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/always-further/nono-py"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1188" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-26T20:39:43Z",
    "nvd_published_at" : null
  }
}