Skip to main content
Menu
CVEs

CVE

Thinkmill Keystatic Core login CSRF in GitHub OAuth callback via missing state check

CVE-2026-129945EUVD-2026-126426GHSA-FV6W-2C5W-H387

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

5.3MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported
Published
Last modified
Reference
Last checked
27/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

Keystatic, from Thinkmill, has a login cross-site request forgery flaw in its GitHub OAuth callback because it skips checking the state value. A remote attacker who gets victims to open a crafted callback link without logging in can sign them in under the attacker's GitHub account, so that edits made in the admin UI are committed under that account.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

Keystatic through 0.6.9 contains a login cross-site request forgery vulnerability in the githubOauthCallback handler that allows unauthenticated remote attackers to sign victims in with the attacker's GitHub account by omitting state validation. Attackers can induce victims to visit the OAuth callback with an attacker-obtained authorization code, causing victim edits in the admin UI to be committed under the attacker's GitHub identity.

cve.now Index

27Pcve.now Index 27 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
  • Reach10/20Affects npm packages
  • Severity5.3/10CVSS 5.3
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 82 if added to CISA KEV
  • Would score about 77 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

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-129945 (Keystatic through 0.6.9 GitHub OAuth Login CSRF via Missing State Validation), 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-129945 (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-129945 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129945 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/generic.ts#L199-L256
- https://github.com/Thinkmill/keystatic/blob/b65d4a55501dc3b7bb268dc925d8538a8a9f8e95/packages/keystatic/src/api/generic.ts#L363-L398
- https://www.vulncheck.com/advisories/keystatic-through-0.6.9-github-oauth-login-csrf-via-missing-state-validation
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-129945
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-129945"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

Evidence 6

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Report
  2. Repository
  3. Repository
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129945

Is CVE-2026-129945 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: cve.now feed data

Which versions are affected by CVE-2026-129945?

@keystatic/core (npm): through 0.6.9.Source: cve.now feed data