CVE-2026-129944 · Package
NO FIX YET
Keystatic through version 0.6.9 has a path traversal flaw in its getIsPathValid check, so paths that share a content directory name prefix are accepted. An unauthenticated remote attacker can read, create, overwrite or delete files outside the intended content directory through the blob, update and tree handlers under /api/keystatic.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites that run Keystatic's API routes (/api/keystatic) with the content directory configured as a path prefix of other directories on the same server. Static-only builds that do not expose the Keystatic API are likely not reachable. The sources do not say which configurations are exposed.
Not affected if auth-required, static-export
Who cares keystatic, node, self-hosted
Unknown from the sources.
No fix yet, per the sources.
Keystatic through 0.6.9 contains a path traversal vulnerability in the getIsPathValid function that allows unauthenticated remote attackers to access sibling paths sharing a content directory name prefix. Attackers can send requests with a no-cors header to the blob, update, and tree handlers under /api/keystatic to read, create, overwrite, or delete files such as posts-evil/pwn.yaml.
This page as .md · .json · CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.