{"answers":{"affected":"2 open source packages ship an affected version, including nono-py.","exploited":"There is no known exploitation of GHSA-m8j6-rc5x-wv36 in the wild and no public exploit code.","fix":"Upgrade nono-py to 0.10.1 or later.","what":"GHSA-m8j6-rc5x-wv36 is a vulnerability in nono-py, published on 26 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-m8j6-rc5x-wv36 and fix it if it is affected.\n\nWhat it is: GHSA-m8j6-rc5x-wv36 is a vulnerability in nono-py, published on 26 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-m8j6-rc5x-wv36 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nono-py (PyPI): affected all versions; fixed in 0.10.1\n- nono-py (PyPI): affected all versions; fixed in 0.10.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-m8j6-rc5x-wv36/ (Markdown: https://insights.sbomify.com/GHSA-m8j6-rc5x-wv36/index.md)","id":"GHSA-m8j6-rc5x-wv36","markdown":"https://insights.sbomify.com/GHSA-m8j6-rc5x-wv36/index.md","name":"GHSA-m8j6-rc5x-wv36","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Python sandboxing library","requires_auth":"none","summary":"Attackers can bypass network restrictions in nono-py sandboxes by exploiting ignored policy fields or missing proxy enforcement, potentially exposing sensitive data.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### 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.","ecosystems":["PyPI"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"nono-py's policy JSON accepts unknown security fields","id":"GHSA-m8j6-rc5x-wv36","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"PyPI","fixed":["0.10.1"],"introduced":["0"],"last_affected":[],"package":"nono-py","purl":null,"source":"GHSA-m8j6-rc5x-wv36"},{"ecosystem":"PyPI","fixed":["0.10.1"],"introduced":["0"],"last_affected":[],"package":"nono-py","purl":"pkg:pypi/nono-py","source":"GHSA-m8j6-rc5x-wv36"}],"products":null,"published":"2026-06-26","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can bypass network restrictions in nono-py sandboxes by exploiting ignored policy fields or missing proxy enforcement, potentially exposing sensitive data.","url":"https://insights.sbomify.com/GHSA-m8j6-rc5x-wv36/"}