# Lupa has a Sandbox escape and RCE due to incomplete attribute_filter enforcement in getattr / setattr

Advisory record · `GHSA-69v7-xpr6-6gjm`

- **Identifiers:** `GHSA-69v7-xpr6-6gjm` · `CVE-2026-34444` · `PYSEC-2026-2613`
- **State:** Confirmed
- **Severity:** CVSS 7.9 High
- **Critical:** No
- **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html) · [CWE-639](https://cwe.mitre.org/data/definitions/639.html) · [CWE-693](https://cwe.mitre.org/data/definitions/693.html) · [CWE-914](https://cwe.mitre.org/data/definitions/914.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [CWE-693](https://agentprime.io/advisories/tag/cwe-693.md) · [CWE-914](https://agentprime.io/advisories/tag/cwe-914.md)
- **Published:** 7 Apr 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 7 Apr 2026, 15:48 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `lupa` (PyPI): affected `<=2.6`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Lupa, versions up to and including 2.6, has a flaw where its attribute_filter is not applied to attribute access made through the getattr and setattr built-ins. An attacker who can run Lua code in an application that relies on attribute_filter as a sandbox can use these built-ins to reach Python internals and run arbitrary commands in the host process. No fixed version is listed. Users can mitigate by disabling the Python builtins with register_builtins=False and not running untrusted Lua code.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.9 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0064, the 50th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:34 UTC: First seen by agentprime
- 31 Oct 2026, 14:34 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-69v7-xpr6-6gjm)

## Sources

- [GitHub Advisory Database: GHSA-69v7-xpr6-6gjm](https://github.com/advisories/GHSA-69v7-xpr6-6gjm)
- [OSV: GHSA-69v7-xpr6-6gjm](https://osv.dev/vulnerability/GHSA-69v7-xpr6-6gjm)
- <https://github.com/scoder/lupa/security/advisories/GHSA-69v7-xpr6-6gjm>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-34444>
- <https://github.com/scoder/lupa>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-69v7-xpr6-6gjm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-69v7-xpr6-6gjm/>. Everything for agents: <https://agentprime.io/llms.txt>.