This page was not yet optimized for use on mobile devices.
CVE-2026-54052
Data
| Vulnerability ID | CVE-2026-54052 |
|---|---|
| Published on | 15.07.2026 21:16 |
| Severity | CRITICAL |
Vulnerable configurations
-
cpe:2.3:a:n8n-mcp:n8n-mcp:2.7.9:*:*:*:*:*:*:*,
cpe:2.3:a:n8n-mcp:n8n-mcp:2.8.1:*:*:*:*:*:*:*,
cpe:2.3:a:n8n-mcp:n8n-mcp:2.9.1:*:*:*:*:*:*:*,
cpe:2.3:a:n8n-mcp:n8n-mcp:2.10.1:*:*:*:*:*:*:*,
cpe:2.3:a:n8n-mcp:n8n-mcp:2.10.2:*:*:*:*:*:*:*,
cpe:2.3:a:n8n-mcp:n8n-mcp:2.10.3:*:*:*:*:*:*:*,
cpe:2.3:a:n8n-mcp:n8n-mcp:2.10.4:*:*:*:*:*:*:*,
cpe:2.3:a:n8n-mcp:n8n-mcp:2.10.5:*:*:*:*:*:*:*,
cpe:2.3:a:n8n-mcp:n8n-mcp:2.10.6:*:*:*:*:*:*:*,
cpe:2.3:a:n8n-mcp:n8n-mcp:2.10.7:*:*:*:*:*:*:*,
…
Vulnerable certificates
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.