{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-53901 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-53901 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-53901 is a high-severity vulnerability in cerebrate, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53901 and fix it if it is affected.\n\nWhat it is: CVE-2026-53901 is a high-severity vulnerability in cerebrate, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-53901 in the wild and no public exploit code.\n\nAffected product: cerebrate. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-53901/ (Markdown: https://insights.sbomify.com/CVE-2026-53901/index.md)","id":"CVE-2026-53901","markdown":"https://insights.sbomify.com/CVE-2026-53901/index.md","name":"CVE-2026-53901","record":{"aliases":["GHSA-g5c4-g774-r8rq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Cerebrate threat sharing","requires_auth":"none","summary":"Attackers can manipulate object identifiers during creation, leading to unauthorized data modification or spoofing in Cerebrate threat sharing platforms.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:L/SA:N/U:Amber","version":"4.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"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.\n\nSuccessful 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cerebrate before v1.37 allows mass assignment of record identifiers during object creation","id":"CVE-2026-53901","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege Escalation in MCO","id":"CVE-2026-53902"},"packages":[],"prev":{"headline":"Cookie injection was possible when opening a PDF link","id":"CVE-2026-53900"},"products":["cerebrate"],"published":"2026-06-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-11","vendors":["cerebrate"]},"summary":"Attackers can manipulate object identifiers during creation, leading to unauthorized data modification or spoofing in Cerebrate threat sharing platforms.","url":"https://insights.sbomify.com/CVE-2026-53901/"}