- Severity: MEDIUM
- CVE: CVE-2026-115565
- Ecosystems: npm
- Packages: storyblok-backup
### Summary
storyblok-backup writes files using unsanitized names for Storyblok components, which are content type or schema definitions. This allows a component name containing path traversal sequences to cause backup files to be written outside the intended backup directory. Anyone with component management access in the source Storyblok space, not server access, can plant a malicious component name that causes arbitrary file writes on the machine of anyone who later runs a backup against that space.
### Details
The writeJson function, which takes a folder, a file name, and content, builds the output file path by directly concatenating the backup directory, the folder, and the file name as strings, with no path sanitization or containment check.
For the components resource type specifically, the file name used is the component’s own name field, which is free text and editable by anyone with component management access in the Storyblok CMS.
Other resource types are not affected by this same issue. Stories and datasources use their numeric IDs as filenames, and assets have their filename derived by splitting on the slash character and taking the last segment, which strips path separators. This issue is scoped specifically to components.
Since the component name is stored in Storyblok and only read back later when the backup tool runs, this is a stored, second order vulnerability. The malicious value is planted once, then triggers on every subsequent backup run performed b…
Source: GitHub Security Advisories · 2026-11-20