nono-py's policy JSON accepts unknown security fields

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.2 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary nono-py policy handling could fail open in two ways. First, resolving a policy-derived ProxyConfig did not automatically enforce CapabilitySet.proxyonly, allowing sandboxed children to bypass a resolved domain allowlist by using direct network access. Second, policy JSON accepted unknown security-sensitive fields, so misspelled or unsupported restrictions could be silently ignored. Impact A sandboxed child may receive broader network access than the policy author intended. This can allow outbound requests outside the configured proxy allowlist and may expose sensitive data depending on the execution environment and workload. Older-kernel note On Linux kernels without Landlock ABI v4 network rules, patched versions continue to support proxy-only enforcement through the seccomp supervisor fallback introduced in 807fb4b. Users on older kernels should ensure policy-resolved proxy configurations are coupled to CapabilitySet.proxyonly(proxy); merely injecting proxy environment…

Published by the source

26 Jun 2026, 20:41 UTC

Last modified by the source

26 Jun 2026, 20:45 UTC

Source last checked

26 Oct 2026, 13:46 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-m8j6-rc5x-wv36

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-m8j6-rc5x-wv36

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-m8j6-rc5x-wv36

Advisory: nono-py's policy JSON accepts unknown security fields
IDs: GHSA-m8j6-rc5x-wv36
Record: https://patchnext.com/advisories/ghsa-m8j6-rc5x-wv36 (revision 2, source checked 26 Oct 2026, 13:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nono-py 0.10.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI nono-py: affected <= 0.10.0; fixed in 0.10.1

## Suggested inspection (read-only)
- `python -m pip show nono-py`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nono-py.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-m8j6-rc5x-wv36 (OSV record GHSA-m8j6-rc5x-wv36 lists affected ranges: PyPI nono-py >=0 <0.10.1 (fixed))
- Verified: https://github.com/advisories/GHSA-m8j6-rc5x-wv36 (GitHub-reviewed advisory GHSA-m8j6-rc5x-wv36 lists affected ranges: PyPI nono-py >=0 <=0.10.0)

Commands are suggestions: review each one before running it.