Information Disclosure in automad/automad (CVE-2026-45332)
Summary
Vulnerability in automad/automad (CVE-2026-45332). Confidential information can be exposed externally. Mitigation: upgrade to 2.0.0-beta.28 or later.
Original description
The description as published by the source.
Automad is a flat-file content management system and template engine. From 2.0.0-alpha.1 to 2.0.0-beta.27, a Broken Access Control vulnerability allows an unauthenticated attacker to retrieve the bcrypt password hash of every administrator account with a single POST request. The /_api/user-collection/create-first-user setup endpoint remains publicly accessible once initial configuration is complete and returns full serialized user data in the JSON response body. This vulnerability is fixed in 2.0.0-beta.28.
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-45332 has been found in automad/automad.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade automad/automad to 2.0.0-beta.28 or later.
If unsure, ask your IT team or search "automad/automad CVE-2026-45332" on the vendor's site.
CVE-2026-45332 (automad/automad) — CWE-200 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.0.0-beta.28 — apply immediately
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.
Information disclosure (CWE-200) exists in automad/automad.
Check the vendor advisory for the affected versions of automad/automad.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 2.0.0-beta.28.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'automad/automad' . 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 'automad/automad' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
automad/automadを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade automad/automad to 2.0.0-beta.28ステージング環境で 2.0.0-beta.28 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com