Skip to main content
VulnerabilityPublished

CVE-2026-115565: storyblok-backup · Stored path traversal via unsanitized Storyblok component names in backup output

Affects storyblok-backupSource GCVE Database

0
Compare
Authoritative record:CVE-2026-115565· Medium 5.7

Not known to be exploited · CVSS 5.7 Medium : upgrade to 0.7.1 when convenient.

Data as of 20 Nov 2026, 16:33 UTC

CVSS 3.1 base score
5.7Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.7
Patch
Available – fixed in 0.7.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade storyblok-backup to 0.7.1.

Affected software

ProductAffectedFixed in
npmstoryblok-backupAffected
  • <0.7.1
Fixed in
  • 0.7.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in storyblok-backup version 0.7.1. Users should upgrade to this version or later to ensure component names are properly sanitized before being used as filenames. The vendor advisory recommends sanitizing component names by applying path segment extraction or verifying that the final path remains within the intended backup directory before writing. Until upgraded, avoid running backups against spaces where untrusted users have component management access.

Description

storyblok-backup versions prior to 0.7.1 contain a stored path traversal vulnerability. This occurs because component names, which are user-editable and unsanitized, are used directly as filenames during backup creation. An attacker with component management access can craft a component name with path traversal sequences to cause files to be written outside the intended backup directory when the backup tool is run. This can lead to arbitrary file writes on the backup host machine.

References

Community reviews

Loading reviews…