Authentication Bypass in statamic/cms (CVE-2026-64665)
Summary
Authentication bypass in statamic/cms (CVE-2026-64665). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 5.74.1 or later.
Original description
The description as published by the source.
Impact
When OAuth login is enabled with a provider that does not guarantee verified email addresses, an unauthenticated attacker could sign in as an existing user — potentially including a super admin — without their password. Exploitation requires OAuth to be explicitly enabled with such a provider.
Patches
Fixed in 5.74.1 and 6.24.0.
Workarounds
Only enable OAuth with providers that guarantee verified email addresses, or disable OAuth login.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-64665 has been found in statamic/cms.
Successful exploitation can lead to full system takeover. CVSS score: 8.1/10.
What to do: upgrade statamic/cms to 5.74.1 or later.
If unsure, ask your IT team or search "statamic/cms CVE-2026-64665" on the vendor's site.
CVE-2026-64665 (statamic/cms) — CWE-287 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 5.74.1 — apply immediately
Workaround: Only enable OAuth with providers that guarantee verified email addresses, or disable OAuth login.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Authentication bypass (CWE-287) exists in statamic/cms.
Check the vendor advisory for the affected versions of statamic/cms.
Severity: High (CVSS 8.1/10). Successful exploitation can lead to full system takeover.
Update to 5.74.1.
Workaround: Only enable OAuth with providers that guarantee verified email addresses, or disable OAuth login.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'statamic/cms' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'statamic/cms' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
statamic/cmsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Only enable OAuth with providers that guarantee verified email addresses, or disable OAuth login.パッチが適用されるまでの応急処置として、Only enable OAuth with providers that guarantee verified email addresses, or disable OAuth login. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade statamic/cms to 5.74.1ステージング環境で 5.74.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com