How severe is CVE-2026-26974?

No CVSS score has been assigned to CVE-2026-26974 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-26974?

CVE-2026-26974 affects the following packages: @tygo-van-den-hurk/slyde (npm). Ecosystems affected: npm.

How do I fix CVE-2026-26974?

Update @tygo-van-den-hurk/slyde to 0.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-26974 is resolved across your whole dependency graph.

How do I detect CVE-2026-26974 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @tygo-van-den-hurk/slyde, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-26974 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2026-26974 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-26974 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-26974?

CVE-2026-26974 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 49th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-26974?

CVE-2026-26974 is classified as CWE-829 (CWE-829). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-26974 published, and has it been updated?

CVE-2026-26974 was published on February 20, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

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

Fix: Tygo-van-den-Hurk/Slyde@e4c215b

CVE-2026-26974 is a CWE-829 vulnerability in @tygo-van-den-hurk/slyde. A fix is available for @tygo-van-den-hurk/slyde — see the affected versions and patch details below.

Sylde has Improper Control of Generation of Code

Also known asGHSA-w7h5-55jg-cq2f

Published

Feb 20, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-26974.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs49th percentile — riskier than 49% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@tygo-van-den-hurk/slydenpm

42downloads / week

Description

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.

Patches

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

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@tygo-van-den-hurk/slyde`	all versions	0.0.5`npm install @tygo-van-den-hurk/slyde@0.0.5`

Affected Products

1 product · 1 configurations

Application

slydeslyde.js

< 0.0.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @tygo-van-den-hurk/slyde, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @tygo-van-den-hurk/slyde to 0.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-26974 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### 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. ### Patches The issue has been **patched in v0.0.5**. Users should upgrade to **v0.0.5 or later** to mitigate the vulnerability. ### Workarounds - Audit and restrict which packages are installed in `node_modules`. ### R

O3 Security · Impact-Aware SCA

Is CVE-2026-26974 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works