CVE-2026-37008
- Published13 Sept 2026
Description
CrewAI before fb2323b offers a Python blocklist approach that operates at the wrong level of abstraction, a different vulnerability than CVE-2026-2275. Import-time blocking of module names does not address the availability of Python's complete object graph. For example, calling ctypes.CDLL(None) loads the C library without relying in any import statements. In other words, a within-process sandbox cannot merely account for the import system and instead must account for the complete runtime of the Python interpreter.
CVSS 3.1 breakdown
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:LRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-37008 being actively exploited?
CVE-2026-37008 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.16%.
How severe is CVE-2026-37008?
CVE-2026-37008 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.16% probability of exploitation.
How do I fix CVE-2026-37008?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-37008 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.