dbcve.org
SlydeApplication · Slyde.js

CVE-2026-26974

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-20
Fix available
A fix is available. Upgrade to 0.0.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Slyde is a program that creates animated presentations from XML. In versions 0.0.4 and below, Node.js automatically imports **/*.plugin.{js,mjs} files including those from node_modules, so any malicious package with a .plugin.js file can execute arbitrary code when installed or required. All projects using this loading behavior are affected, especially those installing untrusted packages. This issue has been fixed in version 0.0.5. To workaround this issue, users can audit and restrict which packages are installed in node_modules.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Slyde versions 0.0.4 and below use a glob pattern that automatically imports all *.plugin.js and *.plugin.mjs files, including those from node_modules. This allows any malicious package to execute arbitrary code when installed or required, creating a critical supply chain attack vector.

MitigationUpgrade to version 0.0.5 to remediate. As a workaround, audit and restrict which packages are installed in node_modules to prevent untrusted code execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SlydeApplication
Affected:< 0.0.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Slyde version
    Run 'npm list slyde' or inspect your project's package.json dependencies to find the installed version of slyde
    Affected if Installed version is 0.0.4 or below, or if no version is listed but the package is present and predates version 0.0.5
  2. Identify glob pattern usage in Slyde code
    Search the Slyde package source code (in node_modules/slyde) for glob patterns matching '*.plugin.js' or '*.plugin.mjs', typically found in plugin loading logic
    Affected if Glob patterns like '**/*.plugin.js' or '**/*.plugin.mjs' are present and used to automatically discover/load plugins
  3. Verify node_modules plugin loading is possible
    Examine how Slyde loads plugins - check if the glob pattern includes the node_modules directory path or uses a relative path that traverses into node_modules
    Affected if The glob pattern is configured to search in directories that include node_modules, allowing automatic loading of plugins from installed packages
  4. Check for untrusted third-party plugins in node_modules
    Inspect installed packages in node_modules for any files matching *.plugin.js or *.plugin.mjs that you did not explicitly intend to load as plugins
    Affected if Any package in node_modules contains .plugin.js or .plugin.mjs files that Slyde would automatically import due to the vulnerable glob pattern

Your environment is affected if Slyde version is below 0.0.5 AND the glob pattern configuration allows automatic loading of plugin files from node_modules.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.0.5 or later
Fixed in 0.0.5
Vendor patch github.com →
Interim mitigation

Upgrade to version 0.0.5 to remediate. As a workaround, audit and restrict which packages are installed in node_modules to prevent untrusted code execution.

Recommended fix High confidence

Slyde version 0.0.5

  1. Upgrade Slyde to version 0.0.5 or later by running: npm install [email protected] (or npm install slyde@latest)
  2. After upgrading, test that your animated presentations still work correctly
  3. As an additional precaution, audit installed packages in node_modules and remove any untrusted or unnecessary packages

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Slyde Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26974 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26974 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data