BloodHound through 9.4.0, fixed in commit 8f79035, contains a missing authorization vulnerability in the custom-nodes API endpoints that allows any authenticated user to modify the global graph schema. Attackers with valid session tokens can create, update, or delete custom node types affecting all users and tenants by invoking unprotected POST, PUT, and DELETE operations on the custom-nodes endpoints.
CVE-2026-59255
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-15. the CNA's CVSS baseline 7.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(high)
- EG Risk
- 48(Track)EG Risk 48/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 computedSeverity71% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 16%
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 28, 2026
Advisory Details (4)
Auto-updated Jul 15, 2026BloodHound Missing Authorization on Custom Node Management API | Advisories | VulnCheck
https://www.vulncheck.com/advisories/bloodhound-missing-authorization-on-custom-node-management-apifix: enforce opengraph permissions on custom node kind endpoints - BED-8970
Fix merged in SpecterOps/BloodHound PR #2989 on 2026-07-13 — awaiting tagged release
https://github.com/SpecterOps/BloodHound/pull/2989Bug: Missing Authorization on Custom Node Kind Management API Allows Any Authenticated User to Modify Global Graph Schema · Issue #2910 · SpecterOps/BloodHound · GitHub
https://github.com/SpecterOps/BloodHound/issues/2910commit 8f790351349f (SpecterOps/BloodHound)
Fix landed in SpecterOps/BloodHound commit 8f790351349f — awaiting tagged release
https://github.com/SpecterOps/BloodHound/commit/8f790351349fd87bcb04377aba84cba6495825b3Vendor Advisories for CVE-2026-59255(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 31× in last 7d / 60× 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.
- 2026-08-03 18:15 UTCEG score recompute
- 2026-08-03 18:15 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 05:55 UTCGHSA enrichment
- 2026-08-02 17:11 UTCGHSA enrichment
- 2026-08-02 05:00 UTCEG score recompute
- 2026-08-02 05:00 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 16:50 UTCGHSA enrichment
- 2026-08-01 04:40 UTCEG score recompute
- 2026-08-01 04:40 UTCGHSA enrichment
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 16:30 UTCGHSA enrichment
- 2026-07-31 04:16 UTCEG score recompute
- 2026-07-31 04:15 UTCGHSA enrichment
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 16:04 UTCEG score recompute
- 2026-07-30 16:04 UTCGHSA enrichment
- 2026-07-30 03:04 UTCEG score recompute
- 2026-07-30 03:04 UTCGHSA enrichment
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 14:53 UTCGHSA enrichment
- 2026-07-29 02:42 UTCEG score recompute
- 2026-07-29 02:41 UTCGHSA enrichment
Show 35 moreShow fewer
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-28 14:31 UTCGHSA enrichment
- 2026-07-28 02:20 UTCEG score recompute
- 2026-07-28 02:20 UTCGHSA enrichment
- 2026-07-28 00:24 UTCEG score recompute
- 2026-07-28 00:24 UTCGHSA enrichment
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-27 11:56 UTCGHSA enrichment
- 2026-07-26 23:46 UTCEG score recompute
- 2026-07-26 23:46 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 11:34 UTCEG score recompute
- 2026-07-26 11:34 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:21 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 05:59 UTCGHSA enrichment
- 2026-07-16 17:49 UTCGHSA enrichment
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 05:39 UTCGHSA enrichment
- 2026-07-15 17:29 UTCEG score recompute
- 2026-07-15 17:28 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p91CRITICAL
- CVE-2018-1217EG 9.8EPSS p99CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-59255?
When was CVE-2026-59255 disclosed?
Is CVE-2026-59255 actively exploited?
What is the CVSS score of CVE-2026-59255?
How do I remediate CVE-2026-59255?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59255
Is Your Infrastructure Affected by CVE-2026-59255?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.