# CVE-2026-53911: Cerebrate primary key mass assignment in CRUD edit operations allows authenticated users to overwrite unrelated records


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 11 Jun 2026
- **Updated:** 11 Jun 2026
- **Also known as:** GHSA-ccc2-wrmm-mgwp

## What is CVE-2026-53911?

CVE-2026-53911 is a medium-severity vulnerability in cerebrate, published on 11 Jun 2026. 

### Official description

Cerebrate before version 1.37 allowed the id primary key field to be supplied through request input during CRUD edit operations and certain custom entity patching flows. In affected entities that did not explicitly mark id as inaccessible, an authenticated attacker could submit a crafted edit request containing the id of another record, causing the save operation to update that unrelated record instead of the record identified by the route parameter. The issue affected several entity types inheriting permissive mass-assignment defaults, including User, Role, UserSetting, LocalTool, PermissionLimitation, and EnumerationCollection. Since UserSettings edit functionality was reachable by any authenticated user, exploitation could allow unauthorized modification of records within the same entity type, with impact depending on the affected endpoint and writable fields. Cerebrate 1.37 fixes this by stripping id from request input after marshalling callbacks and by globally marking id as inaccessible in the base AppModel entity.

The discovery of those potential vulnerabilities are inherited from initial finding from Jeroen Pinoy additional support from AI-Assisted Optus 4.8 (the commit wrongly assign Claude Fable 5 as the model switched) and coordinated by Andras Iklody.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-53911 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53911 is a medium-severity vulnerability in cerebrate, published on 11 Jun 2026. 
Exploitation: There is no known exploitation of CVE-2026-53911 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-53911/ (Markdown: https://insights.sbomify.com/CVE-2026-53911/index.md)
```

## Sources

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

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