CVE-2026-85241: SpecterOps BloodHound Graph Write Endpoint v2.go NewV2API improper authorization

Published Sep 3, 2026
·
Updated

A weakness has been identified in SpecterOps BloodHound up to 9.5.1. The affected element is the function NewV2API of the file cmd/api/src/api/registration/v2.go of the component Graph Write Endpoint. Executing a manipulation can lead to improper authorization. It is possible to launch the attack remotely. Upgrading to version 9.6.0-rc1, 9.6.0 and 9.7.0-rc3 is sufficient to fix this issue. This patch is called 39d1276a63e95a7713f954dea632a19651d9cebb. You should upgrade the affected component.

Affected Software

1 affected component
SpecterOps BloodHound Graph Write Endpoint<=9.5.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade SpecterOps BloodHound Graph Write Endpoint v2.go NewV2API to a version that resolves this vulnerability.

    Fixed in 9.6.0-rc1Patch 39d1276a63e95a7713f954dea632a19651d9cebb
  2. Upgrade

    Upgrade SpecterOps BloodHound Graph Write Endpoint v2.go NewV2API to a version that resolves this vulnerability.

    Fixed in 9.6.0Patch 39d1276a63e95a7713f954dea632a19651d9cebb
  3. Upgrade

    Upgrade SpecterOps BloodHound Graph Write Endpoint v2.go NewV2API to a version that resolves this vulnerability.

    Fixed in 9.7.0-rc3Patch 39d1276a63e95a7713f954dea632a19651d9cebb

Event History

Sep 3, 2026
CVE Published
via MITRE·10:30 PM
Data Sourced
via MITRE·10:30 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

SpecterOps BloodHound versions up to 9.5.1 are affected in the Graph Write Endpoint component, specifically the NewV2API function in cmd/api/src/api/registration/v2.go.

2

What access does an attacker need?

The issue can be exploited remotely and requires low-level privileges. No user interaction is required.

3

What is the impact of successful exploitation?

Successful manipulation can result in improper authorization, with low impact to confidentiality, integrity, and availability.

4

Which versions resolve the issue?

Upgrade the affected component to 9.6.0-rc1, 9.6.0, or 9.7.0-rc3. The fix is identified as patch 39d1276a63e95a7713f954dea632a19651d9cebb.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203