What is CVE-2026-26974?

CVE-2026-26974 is a high-severity security vulnerability in @tygo-van-den-hurk/slyde (npm), affecting versions < 0.0.5. It is fixed in 0.0.5.

Which versions of @tygo-van-den-hurk/slyde are affected by CVE-2026-26974?

@tygo-van-den-hurk/slyde (npm) versions < 0.0.5 is affected.

Is there a fix for CVE-2026-26974?

Yes. CVE-2026-26974 is fixed in 0.0.5. Upgrade to this version or later.

Is CVE-2026-26974 exploitable, and should I be worried?

Whether CVE-2026-26974 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-26974 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-26974?

Upgrade @tygo-van-den-hurk/slyde to 0.0.5 or later.

CVE-2026-26974 in @tygo-van-den-hurk/slyde

Q: Which versions of @tygo-van-den-hurk/slyde are affected by CVE-2026-26974?

@tygo-van-den-hurk/slyde (npm) versions < 0.0.5 is affected.

Q: Is there a fix for CVE-2026-26974?

Yes. CVE-2026-26974 is fixed in 0.0.5. Upgrade to this version or later.

Q: Is CVE-2026-26974 exploitable, and should I be worried?

Whether CVE-2026-26974 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-26974 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-26974?

Upgrade @tygo-van-den-hurk/slyde to 0.0.5 or later.

Summary

Improper Control of Generation of Code ('Code Injection') in @tygo-van-den-hurk/slyde

Workarounds

Audit and restrict which packages are installed in node_modules.

References

CWE-94: Improper Control of Generation of Code
GitHub Security Advisories documentation: https://docs.github.com/en/code-security/security-advisories

Impact

This is a remote code execution (RCE) vulnerability. Node.js automatically imports **/*.plugin.{js,mjs} files including those from node_modules, so any malicious package with a .plugin.js file could execute arbitrary code when installed or required. All projects using this loading behavior are affected, especially those installing untrusted packages.

Affected versions

@tygo-van-den-hurk/slyde (< 0.0.5)

Security releases

@tygo-van-den-hurk/slyde → 0.0.5 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The issue has been patched in v0.0.5. Users should upgrade to v0.0.5 or later to mitigate the vulnerability.

Frequently Asked Questions

What is CVE-2026-26974? CVE-2026-26974 is a high-severity security vulnerability in @tygo-van-den-hurk/slyde (npm), affecting versions < 0.0.5. It is fixed in 0.0.5.
Which versions of @tygo-van-den-hurk/slyde are affected by CVE-2026-26974? @tygo-van-den-hurk/slyde (npm) versions < 0.0.5 is affected.
Is there a fix for CVE-2026-26974? Yes. CVE-2026-26974 is fixed in 0.0.5. Upgrade to this version or later.
Is CVE-2026-26974 exploitable, and should I be worried? Whether CVE-2026-26974 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-26974 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-26974? Upgrade @tygo-van-den-hurk/slyde to 0.0.5 or later.