Quick answers
- Is CVE-2026-53901 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53901 being exploited in the wild.
- How severe is CVE-2026-53901?
- Informational severity, with a CVSS score of 8.7, published 11 June 2026.
- Which products and versions are affected?
- Cerebrate Project Cerebrate before 1.37.
- Is there a fix for CVE-2026-53901?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-53901 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-53901?
- Check whether you run Cerebrate Project Cerebrate at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A mass-assignment vulnerability exists in the generic CRUD 'add' path of Cerebrate. The 'add()' handler attempted to remove an attacker-supplied 'id' from the parameters before the input was normalized via the '__massageInput()' function. Because normalization could re-introduce or retain an 'id' field, an attacker could supply a custom identifier that should be server-controlled. This allows for the creation of objects with arbitrary IDs, leading to potential object spoofing or identifier collisions. The vulnerability was addressed in version 1.37 by ensuring the 'id' is removed from the normalized input immediately before entity patching.
Affected products
- Cerebrate Project Cerebrate before 1.37
Timeline
- 2026-06-11: disclosed
- 2026-06-11: advisory: NVD publication date