CVE-2026-45248: Hedera Guardian Authentication Bypass Information Disclosure
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.
Security readout for executives and security teams
Plain-English summary
Hedera Guardian through 3.5.1 exposes a demo registered-users API without authentication. An outsider could read registered-user metadata, including usernames, Hedera DIDs, registry DIDs, system roles, and policy role assignments. This is not reported as remote code execution, but it can expose sensitive identity and authorization structure.
Executive priority
Prioritize remediation for internet-facing or production Guardian systems because the flaw can reveal identity and authorization metadata without login. The business risk is privacy, reconnaissance, and trust impact, not confirmed system takeover.
Technical view
CVE-2026-45248 is a CWE-306 missing-authentication issue in GET /api/v1/demo/registered-users. The CVSS 4.0 score is 6.9. The source bundle describes unauthenticated network access and limited confidentiality impact, with no stated integrity, availability, or scope impact.
Likely exposure
Organizations running Hedera Guardian through 3.5.1 are potentially exposed if the Guardian API or demo route is reachable by untrusted users. Internet-facing deployments carry the clearest risk. Internal-only deployments may still expose user and role metadata to anyone with network access.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not claim active exploitation. The issue requires no privileges or user interaction, but the documented impact is information disclosure rather than system compromise.
Researcher notes
Evidence supports missing authentication and sensitive metadata disclosure, but the provided bundle does not name a fixed release, workaround, or exploitation in the wild. Avoid assuming broader Guardian compromise beyond the documented endpoint and data fields.
Mitigation direction
Check Hashgraph Guardian guidance and the linked PR for fixed-version availability.
Restrict untrusted access to Guardian demo/API routes until remediation is confirmed.
Review whether demo endpoints are enabled in production deployments.
Apply vendor-provided updates or configuration guidance when available.
Treat disclosed DIDs, usernames, and role data as sensitive exposure.
Validation and detection
Inventory Hedera Guardian deployments and identify versions through 3.5.1.
Confirm whether the registered-users demo route is reachable from untrusted networks.
Verify that sensitive user listings require authentication in production.
Review access logs for unauthenticated requests to the affected route.
Document exposed usernames, DIDs, registries, and role mappings if leakage occurred.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-306 · source CWE mapping
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.