CVE-2026-45248
Description
Hedera Guardian through 3.5.1 contains an authentication bypass vulnerability in the GET /api/v1/demo/registered-users endpoint that allows unauthenticated attackers to retrieve sensitive user information. Attackers can access the endpoint without providing authentication credentials to obtain usernames, Hedera DIDs, parent registry DIDs, system roles, and policy role assignments for all registered users in the system.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Hedera Guardian through 3.5.1 exposes user data via an unauthenticated endpoint, allowing attackers to retrieve sensitive user information without credentials.
Vulnerability
The GET /api/v1/demo/registered-users endpoint in Hedera Guardian through version 3.5.1 lacks authentication checks, allowing unauthenticated access. This endpoint returns sensitive user information including usernames, Hedera DIDs, parent registry DIDs, system roles, and policy role assignments for all registered users. The vulnerability is classified as CWE-306 (Missing Authentication for Critical Function) [1][2].
Exploitation
An attacker can simply send a GET request to /api/v1/demo/registered-users without any authentication token. No prior access or user interaction is required. The endpoint is publicly accessible, and the attacker can retrieve the full list of registered users and their associated sensitive data [1][2].
Impact
Successful exploitation allows an unauthenticated attacker to obtain a comprehensive list of all registered users along with their Hedera DIDs, parent registry DIDs, system roles, and policy role assignments. This information disclosure can be used for further targeted attacks or reconnaissance against the Hedera Guardian system [2].
Mitigation
The fix was implemented in pull request #6076, which adds the @Auth(Permissions.DEMO_KEY_CREATE) guard to the registeredUsers() function, requiring authentication. The fix is available in versions after 3.5.1. Users should update to the latest patched version. No workaround is documented; the endpoint should be restricted until patched [1].
AI Insight generated on May 21, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
2News mentions
0No linked articles in our index yet.