storyblok-backup file overwrite via path traversal in backup naming
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 0.7.1
- Who is exposed
- Not reported
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
Original 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
Upgrade to a fixed version: 0.7.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Affected versions
- webflorist storyblok-backupfixed in 0.7.1
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.7/10CVSS 5.7
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 43 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · webflorist/storyblok-backup · Advisory GHSA-vcx7-pfrh-mcfg |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-115565 |
| Record | NVD · CVE-2026-115565 |
| Other links 2 | |
| Repository | GitHub · webflorist/storyblok-backup · Commit f4e4bb19 |
| Repository | GitHub · webflorist/storyblok-backup · Release v0.7.1 |
Questions about CVE-2026-115565
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: cve.now feed data
Which versions are affected by CVE-2026-115565?
storyblok-backup: before 0.7.1.
Source: cve.now feed data
How do I fix CVE-2026-115565?
Upgrade to a fixed version: 0.7.1.
Source: cve.now feed data
Related
- CVE-2026-77312Flyto2 Core: Arbitrary file write via unguarded data.*/file. modules (incomplete fix of CVE-2026-67429)
- CVE-2026-114516Etherpad: Pre-auth arbitrary file read
- CVE-2026-131202Remote Code Execution (RCE) through REST API Path Traversal in Splunk Enterprise Security
- CVE-2026-131270Path Traversal through the REST API in Splunk SOAR
- CVE-2026-81430Dimension Arbitrary File Write in System Upgrade Process
- CVE-2026-84273IBM Guardium Data Protection Path Traversal
No corrections so far. Something wrong on this page? Report an error.