# CVE-2026-59255: BloodHound Missing Authorization on Custom Node Management API

> Authenticated attackers can modify the global graph schema by accessing unprotected custom node API endpoints in BloodHound.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-7qmq-x64g-8v7j

## What is CVE-2026-59255?

CVE-2026-59255 is a high-severity missing authorization vulnerability in SpecterOps BloodHound, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-59255?


## How do I fix CVE-2026-59255?

No fix has been published for CVE-2026-59255 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-59255 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59255 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59255 and fix it if it is affected.

What it is: CVE-2026-59255 is a high-severity missing authorization vulnerability in SpecterOps BloodHound, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59255 exists.

Affected product: SpecterOps BloodHound. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59255/ (Markdown: https://insights.sbomify.com/CVE-2026-59255/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59255
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59255
- OSV: https://osv.dev/vulnerability/CVE-2026-59255

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59255/
Summaries are generated and may contain mistakes; the official description above is the record.