Advisory

GHSA-9j7f-3r4p-pwh6

Also known as: None

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-
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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-06-26 20:39 UTC
Modified
2026-06-26 20:45 UTC

Affected packages and fixes

nono-py

PyPI · All systems

Affected

  • introduced 0, fixed 0.11.0 (ecosystem)

Fixed versions

0.11.0

Fix

  • Fixed version 0.11.0
    pip install --upgrade nono-py==0.11.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences