Intake is a package for finding, investigating, loading and disseminating data. Prior to version 2.0.9, the shell() syntax within parameter default values appears to be automatically expanded during the catalog parsing process. If a catalog contains a parameter default such as shell(), the command may be executed when the catalog source is accessed. This means that if a user loads a malicious catalog YAML, embedded commands could execute on the host system. Version 2.0.9 mitigates the issue by making getshell False by default everywhere.
CVE-2026-33310
HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-03-19. a secondary CVSS source baseline 8.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(medium)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 35%
- KEV
- Not listed
Published
March 24, 2026
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Jul 27, 2026🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available
Command Injection via shell() Expansion in Parameter Defaults · Advisory · intake/intake · GitHub
https://github.com/intake/intake/security/advisories/GHSA-37g4-qqqv-7m99github_commit
commit d0c0b6b57c1c (intake/intake)
Fix landed in intake/intake commit d0c0b6b57c1c — awaiting tagged release
https://github.com/intake/intake/commit/d0c0b6b57c1cb3f73880655ded4a9b0e18e1fd1bPatch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| pip | intake | — | 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.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-07-27 14:30 UTCEG score recompute
- 2026-07-27 14:30 UTCGHSA enrichment
Related CVEs(same CWE)
Same CWE
10 shownCWE-94 · CWE-78
- CVE-2003-1432EG 10.0EPSS p94HIGH
- CVE-2003-0041EG 10.0HIGH
- CVE-2002-0495EG 10.0EPSS p96HIGH
- CVE-2001-1583EG 10.0EPSS p100HIGH
- CVE-1999-0702EG 10.0EPSS p98HIGH
- CVE-1999-0509EG 10.0EPSS p98HIGH
- CVE-1999-0067EG 10.0EPSS p100HIGH
- CVE-1999-0043EG 9.8EPSS p99CRITICAL
- CVE-2005-3650EG 9.3EPSS p93HIGH
- CVE-2005-2368EG 9.3HIGH
Frequently asked(5)
What is CVE-2026-33310?
CVE-2026-33310 is a high vulnerability published on March 24, 2026. Intake is a package for finding, investigating, loading and disseminating data. Prior to version 2.0.9, the shell() syntax within parameter default values appears to be automatically expanded during the catalog parsing process. If a catalog contains a parameter default such as shell(<command>), the…
When was CVE-2026-33310 disclosed?
CVE-2026-33310 was first published in the National Vulnerability Database on March 24, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33310 actively exploited?
CVE-2026-33310 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.9% of all scored CVEs.
What is the CVSS score of CVE-2026-33310?
CVE-2026-33310 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-33310?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33310, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-33310
Is Your Infrastructure Affected by CVE-2026-33310?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.