/

CVE-2026-28766

Severity:

CRITICAL RISK

(9.3)

Missing Authentication / Broken Access Control

CVE-2026-28766

Analyzed

Vulnerability type

Category:

Missing Authentication / Broken Access Control

CWE:

CWE-306

Impact:

Exposure of All User Account Information (Mass Data Disclosure)

Severity:

CRITICAL RISK

(9.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A critical access control flaw in a Gardyn API endpoint exposes complete user account information for all registered users without requiring authentication.

Any party able to reach the vulnerable endpoint can retrieve sensitive account data at scale, turning a simple HTTP request into a serious privacy and security risk.

Affected context

This vulnerability occurs in a Gardyn backend API endpoint responsible for returning user account information.

The endpoint is exposed over the network and fails to enforce any authentication or session validation before serving responses.

The issue is present when:

  • The vulnerable endpoint is reachable from the internet or another untrusted network segment, and
  • The API is configured to return full user account records, and
  • No upstream gateway, WAF, or reverse proxy enforces additional authentication or access checks.

Exploit preconditions

  • Attack surface: Network-accessible HTTP(S) API endpoint.
  • Required access: None beyond the ability to send requests to the API (no account, token, or prior session required).
  • Trigger point: Issuing a request to the specific endpoint that returns user data without verifying the caller's identity.
  • Why exploitation is possible: The endpoint does not implement authentication or authorization controls (CWE-306), so it treats every request as trusted and returns sensitive account information by default.

Why this happens

The core issue is a missing authentication check on an endpoint that returns sensitive user account information.

From a design perspective, this maps to CWE-306: Missing Authentication for Critical Function: a critical data-access function is exposed without verifying the caller's identity or privileges.

Instead of requiring valid credentials, tokens, or session context, the implementation likely routes all requests directly to data retrieval logic, resulting in a public, unauthenticated data disclosure path.

Potential impact

  • Exposure of all registered user account details to any network-level attacker.
  • Large-scale privacy violations, including potential leakage of contact information or other personal data.
  • Increased risk of targeted phishing, social engineering, and account takeover attacks using leaked information.
  • Regulatory and compliance consequences due to unauthorized disclosure of customer data.
  • Reputation damage and loss of user trust if the leak becomes public or is actively exploited.

General mitigation guidance

Mitigation should focus on enforcing strong, consistent authentication for all endpoints that handle user data, and minimizing the amount of data exposed by any single call.

Common defensive patterns include:

  • Requiring validated authentication (e.g., tokens, sessions, API keys) for every endpoint that returns user-specific or sensitive information.
  • Applying authorization checks to ensure that a caller can only access their own data or data within clearly defined roles.
  • Reducing default response scopes so endpoints return only the minimum necessary fields, avoiding broad "list all users" operations.
  • Centralizing authentication and access control logic so that sensitive endpoints cannot bypass security checks.
  • Implementing a secure-by-default API design where unauthenticated access is opt-in, limited to non-sensitive resources, and carefully reviewed.

How teams detect issues like this

Organizations can detect this class of issue using a combination of testing and review techniques:

  • API security testing: Systematically probe endpoints without credentials to verify they do not return sensitive data; integrate this into automated integration or DAST pipelines.
  • Static analysis and code review: Look for controller or route handlers that query user tables or account models without invoking authentication/authorization middleware.
  • Architecture and policy checks: Enforce patterns (e.g., all user-data routes must attach authentication filters) and use linters or policy-as-code to flag exceptions.
  • Logging and monitoring: Monitor for anomalous high-volume requests to user-data endpoints, especially from unauthenticated sources, as potential indicators of exploitation.

Sources

SourceLink
github.comgithub.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-055-03.json
mygardyn.commygardyn.com/security/
cisa.govcisa.gov/news-events/ics-advisories/icsa-26-055-03

Frequently asked

questions

Yes. If the affected endpoint is exposed to the internet or any untrusted network, a remote attacker can exploit it by sending unauthenticated requests.

No. The core problem is that the endpoint does not enforce authentication, so even completely unaffiliated clients can retrieve user account information.

Introduce mandatory authentication and authorization on the endpoint, ensuring that only authenticated users can access account data, and that each user can only retrieve information they are explicitly allowed to see.

Adopt an API design where all data-bearing endpoints are authenticated by default, centralize access control in reusable middleware, and regularly test endpoints without credentials to confirm that sensitive data is never exposed anonymously.

Find out what's already
exploitable in your codebase.