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
HIGHPre-NVD 7.17.1Elevated
EchelonGraph scoreLOW confidence
This high-severity CVE scores 7.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: cna:vulncheck
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 7.1Exploit: NoneExposed: 0
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(low)
- EPSS
- —
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 15, 2026
Advisory Details (4)
Auto-updated Jul 15, 2026Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
generic
BloodHound Missing Authorization on Custom Node Management API | Advisories | VulnCheck
https://www.vulncheck.com/advisories/bloodhound-missing-authorization-on-custom-node-management-apigithub_pr
fix: 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/2989generic
Bug: 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/2910github_commit
commit 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 2× in last 7d / 2× 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-07-15 17:29 UTCEG score recompute
- 2026-07-15 17:28 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
Frequently asked(4)
What is CVE-2026-59255?
CVE-2026-59255 is a high vulnerability published on July 15, 2026. 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…
When was CVE-2026-59255 disclosed?
CVE-2026-59255 was first published in the National Vulnerability Database on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-59255?
CVE-2026-59255 has a CVSS v3 base score of 7.1 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-59255?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59255, 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-59255
Is Your Infrastructure Affected by CVE-2026-59255?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.