# CVE-2026-53912: Cerebrate self-registration password hash exposure via inbox and audit log views

> Authenticated users can retrieve password hashes from self-registration inbox and audit logs, enabling offline cracking attempts.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/S:N/U:Green`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2026
- **Updated:** 11 Jun 2026
- **Also known as:** GHSA-88x3-39g9-9frv

## What is CVE-2026-53912?

CVE-2026-53912 is a medium-severity vulnerability in cerebrate, published on 11 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Cerebrate before version 1.37 exposed credential material from self-registration requests. The self-registration workflow stored the registrant’s hashed password in the inbox message data payload. This payload was returned unredacted through inbox index and view responses, including HTML, JSON, and CSV outputs, and could also be written unredacted into audit log entries for the inbox message.

An authenticated user with sufficient privileges to access inbox entries or related audit logs could retrieve password hashes associated with pending self-registration requests. Although the exposed value is a password hash rather than a plaintext password, disclosure of password hashes may enable offline password-cracking attempts and could increase risk where users reuse passwords across systems.

Cerebrate 1.37 fixes the issue by redacting sensitive password and authkey fields from inbox display/API output and recursively redacting those fields from JSON values written to audit logs, while leaving the stored registration payload intact for account creation processing.

Affected component: Inbox self-registration request handling and audit logging

Fixed version: Cerebrate 1.37

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


## How do I fix CVE-2026-53912?

No fix has been published for CVE-2026-53912 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-53912 being exploited?

There is no known exploitation of CVE-2026-53912 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53912 and fix it if it is affected.

What it is: CVE-2026-53912 is a medium-severity vulnerability in cerebrate, published on 11 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53912 in the wild and no public exploit code.

Affected product: cerebrate. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53912/ (Markdown: https://insights.sbomify.com/CVE-2026-53912/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53912
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53912
- OSV: https://osv.dev/vulnerability/CVE-2026-53912

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53912/
Summaries are generated and may contain mistakes; the official description above is the record.