| Release | BloodHound | OpenHound | SharpHound | AzureHound |
| 2026-06-17 | v9.3.0 | v0.2.1 | No release | v2.12.2 |
Jamf API Client Authentication
Authenticate the OpenHound Jamf collector with a Jamf Pro API client instead of relying on a Jamf user account and password.This update adds support for Jamf API clients as the recommended authentication method. API clients are not tied to a user account, can be scoped to a dedicated API role, and can be rotated or revoked independently, making them a better fit for production environments and least-privilege access.GitHub Enterprise SSO Support
Connect OpenHound to GitHub Enterprise environments that enforce single sign-on at the enterprise level.This update addresses authentication failures in GitHub Enterprise environments where SSO blocked OpenHound from accessing repositories through the configured GitHub App.Role-Based Access Hardening
Read access for the User, Power User, and Read-only roles has been reduced to limit exposure to sensitive user data and administrative API endpoints.This update refines the permission model for administration-related APIs so these roles retain access only to the endpoints and data required for their supported workflows.For example, these roles can use the List Users Minimal endpoint to read user data, but cannot access sensitive information through the broader List Users endpoint.Auditor Access Improvements
Users with the Auditor role can now view the Manage Users and Manage Clients tables without requiring the permissions needed to create or modify those resources.This update adds read-only access to those management views while keeping administrative actions such as Create User, Create Client, and other modification workflows restricted to the Admin role.Expanded Audit Logging
Audit logs now capture additional high-risk user actions, including running Cypher queries, editing collector clients or schedules, and running on-demand collections.This change improves visibility into sensitive operator actions for security reviews and compliance workflows.Accessibility Improvements
Data tables now provide more accessible headers, sorting behavior, keyboard navigation, and screen reader announcements.This update improves table usability across supported browsers and helps align the experience with WCAG 2.1 accessibility requirements.OpenGraph Extension Namespace Visibility
The List OpenGraph Extensions Information endpoint now includes each extension’snamespace key in its response body.This change gives the API and the OpenGraph Management page the information needed to expose the namespace prefix used for extension-defined node types.Full-Path Highlighting
When you select a node in the graph, BloodHound now dims paths that do not traverse the selected node. This includes inbound and outbound object control, making it easier to isolate how a node participates in longer Attack Paths.Full-path highlighting is enabled by default. See Object interaction for more information.Analysis Performance Improvements
Optimized processing logic for the following edge types, significantly reducing time in analysis:Pre-Installed SpecterOps Extensions
Updated Attack Path Type Names
Search Across Certification Statuses
API
Resolved an issue where the Composition and Relay Target accordions in the Entity panel did not populate in the following ADCS edges, causing the related node and edge data to appear empty:Cypher
- Fixed an issue where editing a saved query while another query was selected displayed the wrong query in the edit box, potentially causing you to overwrite the wrong saved query.
- Fixed a performance issue where reusing Cypher query variables caused queries to run significantly slower instead of making them more restrictive as intended.
Posture
Resolved an issue where the the OpenHound Okta collector appeared to connect successfully but returned incomplete data, with relevant Okta-based saved queries returning no results.
edge-* AzureHound container images where an invalid collector version string caused BloodHound to reject uploads from the collector as unsupported.