CVE-2026-53911

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.3
EG Score
6.3(medium)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity63% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
10.9%
KEV
Not listed

Published

June 11, 2026

Last Modified

June 11, 2026

Advisory Details (1)

Auto-updated Jun 13, 2026
Patch available. Sources: github_commit.
github_commit Patch Available

commit b3c8f951b063 (cerebrate-project/cerebrate)

Patch available: cerebrate-project/cerebrate v1.37 (contains commit b3c8f951b063)

https://github.com/cerebrate-project/cerebrate/commit/b3c8f951b0634f05691339512ef06cc261afecaf

Vendor Advisories for CVE-2026-53911(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 63× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:19 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-17 06:37 UTCGHSA enrichment
  12. 2026-07-16 17:03 UTCEPSS rescore
  13. 2026-07-16 02:08 UTCGHSA enrichment
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-15 02:00 UTCEPSS rescore
  18. 2026-07-15 01:44 UTCGHSA enrichment
  19. 2026-07-13 23:35 UTCGHSA enrichment
  20. 2026-07-13 22:31 UTCEPSS rescore
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-12 22:35 UTCGHSA enrichment
  24. 2026-07-12 05:46 UTCEPSS rescore
  25. 2026-07-11 18:17 UTCGHSA enrichment
Show 75 more
  1. 2026-07-10 17:52 UTCGHSA enrichment
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-09 04:30 UTCGHSA enrichment
  5. 2026-07-08 15:16 UTCEPSS rescore
  6. 2026-07-08 15:16 UTCEPSS rescore
  7. 2026-07-08 03:42 UTCGHSA enrichment
  8. 2026-07-07 13:46 UTCEPSS rescore
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-07 03:17 UTCGHSA enrichment
  11. 2026-07-06 16:27 UTCEPSS rescore
  12. 2026-07-06 16:27 UTCEPSS rescore
  13. 2026-07-06 02:23 UTCEPSS rescore
  14. 2026-07-06 02:23 UTCEPSS rescore
  15. 2026-07-06 01:18 UTCGHSA enrichment
  16. 2026-07-05 02:31 UTCEPSS rescore
  17. 2026-07-05 02:30 UTCEPSS rescore
  18. 2026-07-05 00:54 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-04 00:31 UTCGHSA enrichment
  22. 2026-07-03 00:06 UTCGHSA enrichment
  23. 2026-07-01 23:39 UTCGHSA enrichment
  24. 2026-07-01 15:07 UTCEPSS rescore
  25. 2026-06-30 23:22 UTCEPSS rescore
  26. 2026-06-30 23:14 UTCGHSA enrichment
  27. 2026-06-29 22:47 UTCGHSA enrichment
  28. 2026-06-29 14:06 UTCEPSS rescore
  29. 2026-06-29 14:06 UTCEPSS rescore
  30. 2026-06-28 22:24 UTCGHSA enrichment
  31. 2026-06-28 14:07 UTCEPSS rescore
  32. 2026-06-28 04:56 UTCEPSS rescore
  33. 2026-06-28 04:56 UTCEPSS rescore
  34. 2026-06-27 22:00 UTCGHSA enrichment
  35. 2026-06-27 03:08 UTCEPSS rescore
  36. 2026-06-26 21:35 UTCGHSA enrichment
  37. 2026-06-25 21:11 UTCGHSA enrichment
  38. 2026-06-25 13:49 UTCEPSS rescore
  39. 2026-06-24 20:48 UTCGHSA enrichment
  40. 2026-06-24 14:05 UTCEPSS rescore
  41. 2026-06-23 21:33 UTCEPSS rescore
  42. 2026-06-23 21:33 UTCEPSS rescore
  43. 2026-06-23 18:41 UTCGHSA enrichment
  44. 2026-06-22 18:12 UTCGHSA enrichment
  45. 2026-06-22 14:25 UTCEPSS rescore
  46. 2026-06-22 14:25 UTCEPSS rescore
  47. 2026-06-21 15:32 UTCGHSA enrichment
  48. 2026-06-21 14:56 UTCEPSS rescore
  49. 2026-06-21 14:56 UTCEPSS rescore
  50. 2026-06-21 01:59 UTCEPSS rescore
  51. 2026-06-21 01:59 UTCEPSS rescore
  52. 2026-06-20 15:07 UTCGHSA enrichment
  53. 2026-06-19 19:26 UTCEPSS rescore
  54. 2026-06-19 19:26 UTCEPSS rescore
  55. 2026-06-19 14:28 UTCGHSA enrichment
  56. 2026-06-18 17:52 UTCEPSS rescore
  57. 2026-06-18 17:52 UTCEPSS rescore
  58. 2026-06-18 14:03 UTCGHSA enrichment
  59. 2026-06-17 17:53 UTCEPSS rescore
  60. 2026-06-17 13:38 UTCGHSA enrichment
  61. 2026-06-16 17:53 UTCEPSS rescore
  62. 2026-06-16 13:14 UTCGHSA enrichment
  63. 2026-06-15 17:49 UTCEPSS rescore
  64. 2026-06-15 17:49 UTCEPSS rescore
  65. 2026-06-15 12:47 UTCGHSA enrichment
  66. 2026-06-14 23:18 UTCEPSS rescore
  67. 2026-06-14 12:22 UTCGHSA enrichment
  68. 2026-06-13 23:00 UTCEPSS rescore
  69. 2026-06-13 11:59 UTCGHSA enrichment
  70. 2026-06-12 23:12 UTCEPSS rescore
  71. 2026-06-12 23:12 UTCEPSS rescore
  72. 2026-06-12 11:35 UTCGHSA enrichment
  73. 2026-06-11 14:00 UTCEPSS rescore
  74. 2026-06-11 11:11 UTCEG score recompute
  75. 2026-06-11 11:11 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53911?
CVE-2026-53911 is a medium vulnerability published on June 11, 2026. 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…
When was CVE-2026-53911 disclosed?
CVE-2026-53911 was first published in the National Vulnerability Database on June 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53911 actively exploited?
CVE-2026-53911 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 10.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53911?
CVE-2026-53911 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-53911?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53911, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53911

Explore →

Is Your Infrastructure Affected by CVE-2026-53911?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.