Security readout for executives and security teams
Plain-English summary
Lupa is a Python package that embeds Lua. In version 2.6 and earlier, its sandbox restrictions can be bypassed through normal attribute access helpers, which may let an attacker escape intended limits and run code. This is high impact where untrusted Lua code is accepted.
Executive priority
Prioritize remediation for internet-facing or multi-tenant systems that execute Lua through Lupa. Treat this as urgent where the sandbox is a security boundary, because successful exploitation can become remote code execution.
Technical view
The issue is incomplete enforcement of Lupa's attribute_filter for getattr and setattr-style access. That weakens object access controls in the Python-Lua boundary and can lead to sandbox escape and arbitrary code execution. The CVSS 3.1 score is 8.1 with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely in services that use scoder Lupa <= 2.6 to run untrusted or semi-trusted Lua/LuaJIT code inside CPython. Applications using Lupa only for fully trusted internal scripts have lower practical risk but should still update.
Exploitation context
The bundle does not show CISA KEV listing or confirmed active exploitation. The CVSS vector is network reachable with no privileges or user interaction, but high attack complexity, suggesting exploitation depends on application-specific access to Lupa sandboxed execution.
Researcher notes
Affected product evidence names scoder Lupa <= 2.6. The public bundle attributes the weakness to inconsistent attribute_filter enforcement through getattr and setattr. No exploit status, proof-of-concept, or precise fixed upstream version is included here.
Mitigation direction
- Inventory Python environments for scoder Lupa and identify versions <= 2.6.
- Check upstream GHSA and distro advisories for the fixed package version.
- Apply vendor-provided updates where available, including relevant Red Hat errata.
- Avoid running untrusted Lua through Lupa until remediated or strongly isolated.
- Review sandbox assumptions around attribute_filter use in affected applications.
Validation and detection
- Confirm installed Lupa versions in production, CI, containers, and build lockfiles.
- Identify code paths that execute user-supplied or tenant-controlled Lua.
- Verify updated packages are deployed and old runtime images are retired.
- Review dependency scanners for CVE-2026-34444 coverage and suppressions.
- Confirm no application logic relies on attribute_filter as the only trust boundary.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-914: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-34444 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9redhat-SADPCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
7.9HighVector: 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
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-04-06T16:02:58.221Z: Reported to Red Hat.
- 2026-04-06T15:30:30.525Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/scoder/lupa/security/advisories/GHSA-69v7-xpr6-6gjmCVE reference, GitHub_M · x_refsource_CONFIRM
- https://access.redhat.com/security/cve/CVE-2026-34444CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2455413CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-34444.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:22993CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Dynamically-Identified Variables
Improper Control of Dynamically-Identified Variables represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.