CVE-2026-34444

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 10.0 from GitHub Security Advisory (severity: HIGH) published 2026-04-07. NVD baseline CVSS 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-19346 (ENISA EUVD) · GHSA-69v7-xpr6-6gjm (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Lupa integrates the runtimes of Lua or LuaJIT2 into CPython. In 2.6 and earlier, attribute_filter is not consistently applied when attributes are accessed through built-in functions like getattr and setattr. This allows an attacker to bypass the intended restrictions and eventually achieve arbitrary code execution.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
61
EG Risk 61/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
49th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 6, 2026

Last Modified

October 26, 2026

Advisory Details (5)

Auto-updated Oct 26, 2026
🔬 Proof of concept available. Patch available. Sources: github, redhat.
Red HatMentions a patch (unverified)
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-34444.json
Red Hat

2455413 – (CVE-2026-34444) CVE-2026-34444 lupa: Lupa: Arbitrary Code Execution due to inconsistent attribute filtering

https://bugzilla.redhat.com/show_bug.cgi?id=2455413
Red HatMentions a patch (unverified)

CVE-2026-34444 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-34444
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:22993
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Sandbox escape and RCE due to incomplete attribute_filter enforcement in getattr / setattr · Advisory · scoder/lupa · GitHub

https://github.com/scoder/lupa/security/advisories/GHSA-69v7-xpr6-6gjm

Vendor Advisories for CVE-2026-34444(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatsatellite/foreman-mcp-server-rhel9:17804920082026-06-03redhat
piplupa—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-lupa1.10+dfsg-1 ... 2.4+dfsg-1 (6 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-lupa1.14.1+dfsg-1, 2.2+dfsg-1, 2.4+dfsg-1
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-lupa2.4+dfsg-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-lupa2.4+dfsg-1
  • every version on: no fix on record
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
lupa0.1 ... 2.6 (46 versions)
  • every version through 2.6: no fix on record
—

Weakness Classification(4)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 32× in last 7d / 105× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 412 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 312 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 01:42 UTCEG score recompute
  2. 2026-11-02 01:42 UTCVendor advisory
  3. 2026-11-02 01:42 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  4. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  5. 2026-11-01 03:39 UTCEG score recompute
  6. 2026-11-01 03:39 UTCVendor advisory
  7. 2026-11-01 03:39 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  8. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  9. 2026-10-31 05:35 UTCEG score recompute
  10. 2026-10-31 05:35 UTCVendor advisory
  11. 2026-10-31 05:35 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  12. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  13. 2026-10-30 07:32 UTCEG score recompute
  14. 2026-10-30 07:32 UTCVendor advisory
  15. 2026-10-30 07:32 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  16. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  17. 2026-10-29 09:28 UTCEG score recompute
  18. 2026-10-29 09:28 UTCVendor advisory
  19. 2026-10-29 09:28 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  20. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  21. 2026-10-28 11:24 UTCEG score recompute
  22. 2026-10-28 11:24 UTCVendor advisory
  23. 2026-10-28 11:23 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  24. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  25. 2026-10-27 12:52 UTCVendor advisory
Show 75 more
  1. 2026-10-27 12:52 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  2. 2026-10-26 21:28 UTCVendor advisory
  3. 2026-10-26 21:28 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  4. 2026-10-26 19:58 UTCEG score recompute
  5. 2026-10-26 19:58 UTCVendor advisory
  6. 2026-10-26 19:57 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  7. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  8. 2026-10-25 19:48 UTCEG score recompute
  9. 2026-10-25 19:48 UTCVendor advisory
  10. 2026-10-25 19:48 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  12. 2026-10-25 14:33 UTCEG score recompute
  13. 2026-10-24 21:43 UTCEG score recompute
  14. 2026-10-24 21:43 UTCVendor advisory
  15. 2026-10-24 21:43 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  16. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  17. 2026-10-23 23:40 UTCEG score recompute
  18. 2026-10-23 23:40 UTCVendor advisory
  19. 2026-10-23 23:40 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  20. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  21. 2026-10-23 01:04 UTCEG score recompute
  22. 2026-10-23 01:04 UTCVendor advisory
  23. 2026-10-23 01:04 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  24. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  25. 2026-10-22 02:19 UTCEG score recompute
  26. 2026-10-22 02:19 UTCVendor advisory
  27. 2026-10-22 02:19 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  28. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  29. 2026-10-21 04:00 UTCEG score recompute
  30. 2026-10-21 04:00 UTCVendor advisory
  31. 2026-10-21 04:00 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  32. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  33. 2026-10-20 05:55 UTCEG score recompute
  34. 2026-10-20 05:55 UTCVendor advisory
  35. 2026-10-20 05:55 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  36. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  37. 2026-10-19 07:48 UTCEG score recompute
  38. 2026-10-19 07:48 UTCVendor advisory
  39. 2026-10-19 07:48 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  40. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  41. 2026-10-18 09:30 UTCVendor advisory
  42. 2026-10-18 09:30 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  43. 2026-10-18 03:45 UTCEG score recompute
  44. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  45. 2026-10-17 06:22 UTCEG score recompute
  46. 2026-10-17 06:22 UTCVendor advisory
  47. 2026-10-17 06:22 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  48. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  49. 2026-10-16 07:41 UTCEG score recompute
  50. 2026-10-16 07:41 UTCVendor advisory
  51. 2026-10-16 07:41 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  52. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  53. 2026-10-15 06:39 UTCEG score recompute
  54. 2026-10-15 06:39 UTCVendor advisory
  55. 2026-10-15 06:38 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  56. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  57. 2026-10-14 02:19 UTCEG score recompute
  58. 2026-10-14 02:19 UTCVendor advisory
  59. 2026-10-14 02:19 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  60. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  61. 2026-10-12 22:36 UTCEG score recompute
  62. 2026-10-12 22:36 UTCVendor advisory
  63. 2026-10-12 22:35 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  64. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  65. 2026-10-12 16:12 UTCEG score recompute
  66. 2026-10-12 08:20 UTCVendor advisory
  67. 2026-10-12 08:19 UTCGHSA enrichmentGHSA-69v7-xpr6-6gjm · GitHub severity HIGH · GitHub CVSS 10.0
  68. 2026-10-11 19:54 UTCEG score recompute
  69. 2026-10-11 17:08 UTCEG score recompute
  70. 2026-10-11 14:35 UTCEG score recompute
  71. 2026-10-11 14:06 UTCOSV refresh
  72. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  73. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  74. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  75. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.8% · 55th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-34444?
CVE-2026-34444 is a critical-severity vulnerability; its CVE record was published on April 6, 2026. Lupa integrates the runtimes of Lua or LuaJIT2 into CPython. In 2.6 and earlier, attribute_filter is not consistently applied when attributes are accessed through built-in functions like getattr and setattr. This allows an attacker to bypass the intended restrictions and eventually achieve…
When was the CVE record for CVE-2026-34444 published?
The CVE record for CVE-2026-34444 was published on April 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-34444 actively exploited?
CVE-2026-34444 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-34444?
CVE-2026-34444 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-34444?
A fix for CVE-2026-34444 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-34444 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-34444

Explore →

Is Your Infrastructure Affected by CVE-2026-34444?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs