BloodHound Has Changed. Your Course Probably Hasn’t.

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

BloodHound has moved fast and not all courses have kept up. If you create or maintain a course or training that includes BloodHound, now is a good time to review your materials.

BloodHound Community Edition (BHCE) has continued to evolve rapidly, with v8.9 releasing just last week. There have been many updates that apply to both manual installations and the version bundled with Kali Linux. Alongside these changes, we introduced the OpenGraph, which extends BloodHound beyond Active Directory and Entra ID into systems like AWS, GitHub, and Jamf.

We also remain committed to maintaining BloodHound as an open-source project. 

Four out of five courses we reviewed still used a BloodHound version that is three years out of date. Many courses rely on Kali Linux, where we still packaged BloodHound Legacy until August 2025. Sharing a few updates here in case you’re planning a refresh, so learners can take advantage of the latest capabilities.

What to Update in Your Course

Here are a few updates that may be helpful as you revise your material.

BloodHound CLI for manual installations: If you are installing BloodHound on a custom system rather than using the pre-installed version on Kali Linux, use BloodHound CLI. It pulls and configures the correct Docker containers for a consistent setup.

BloodHound v8 for coursework: BloodHound has seen significant UX and functionality improvements since v4 (BloodHound Legacy). We recommend using v8 or later for all coursework. You can reference or reuse content from the public documentation. 

Cover OpenGraph in your coursework: BloodHound v8 …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://specterops.io/blog/2026/04/11/bloodhound-course-update/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.