Vulnerability in Cerebrate (CVE-2026-53901)
Summary
Vulnerability in Cerebrate (CVE-2026-53901). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.37 or later.
Original description
The description as published by the source.
Cerebrate before version 1.37 contains a mass-assignment vulnerability in the generic CRUD add path. The add() handler attempted to remove an attacker-supplied id from $params before normalizing the request through __massageInput(). Because the normalized $input could still contain an id field, a user able to reach an affected add endpoint could supply an identifier that should have been server-controlled.
Successful exploitation could allow creation of objects with attacker-chosen identifiers, potentially causing unauthorized data manipulation, object spoofing, inconsistent references, or disruption through identifier collisions, depending on the affected model and endpoint permissions. The issue was fixed in v1.37 by removing id from the normalized input before entity patching.
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-53901 has been found in Cerebrate.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Cerebrate to 1.37 or later.
If unsure, ask your IT team or search "Cerebrate CVE-2026-53901" on the vendor's site.
CVE-2026-53901 (Cerebrate) — CWE-20
Patched: 1.37 — 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.
A vulnerability (CWE-20) exists in Cerebrate.
Check the vendor advisory for the affected versions of Cerebrate.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.37.
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 'Cerebrate' . 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 'Cerebrate' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Cerebrateを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Cerebrate to 1.37ステージング環境で 1.37 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- web github.com