{"items":[{"id":"NVI-00017467","kind":"vulnerability","title":"nono-py's policy JSON accepts unknown security fields","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-m8j6-rc5x-wv36"],"plain_summary":"GitHub lists this reviewed advisory for nono-py. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-03de984b24953d19d33b9bcd0766685e"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-26T20:43:29.000Z","value":"5.2 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-03de984b24953d19d33b9bcd0766685e"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-03de984b24953d19d33b9bcd0766685e","url":"https://github.com/advisories/GHSA-m8j6-rc5x-wv36","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-m8j6-rc5x-wv36","publisher":"GitHub Advisory Database","observed_at":"2026-11-05T19:05:53.922Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-03de984b24953d19d33b9bcd0766685e"],"technology":"nono-py","known_exclusions":[],"conditions_summary":"### Summary\n\nnono-py policy handling could fail open in two ways. First, resolving a policy-derived `ProxyConfig` did not automatically enforce `CapabilitySet.proxy_only`, 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.\n\n### Impact\n\nA 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.\n\n### Older-kernel note\n\nOn 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.proxy_only(proxy);` merely injecting proxy environment variables is not sufficient.","public_affected_ranges":["<= 0.10.0"]}],"null_published_at":"2026-11-05T19:10:21.392Z","source_updated_at":"2026-06-26T20:43:29.000Z","source_disclosed_at":"2026-06-26T20:41:59.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-05T19:05:53.922Z"}],"next_cursor":null,"snapshot_revision":"42594"}