/

CVE-2026-75338

Severity:

CRITICAL RISK

(9.8)

Broken Access Control (CWE-284) in disconf Config APIs

CVE-2026-75338

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized Disclosure of Configuration Data

Severity:

CRITICAL RISK

(9.8)

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

disconf 2.6.36 exposes several configuration-fetching APIs without authentication because they are explicitly whitelisted by the login interceptor. An anonymous attacker may read configuration items and files managed by the configuration center, potentially revealing secrets and sensitive operational data.

Affected context

The vulnerability occurs in disconf deployments where the following configuration-fetching routes remain reachable without an authenticated session:

  • /api/config/item
  • /api/config/file
  • /api/config/list
  • /api/config/simple/list

Risk depends on network exposure and on whether the configuration center contains credentials, tokens, internal service details, or other sensitive values.

Exploit preconditions

  • Attack surface: HTTP configuration-management APIs
  • Required access: Network connectivity to the disconf service; no valid account may be required
  • Trigger point: Requests to the exposed configuration-fetching endpoints
  • Why exploitation is possible: The login interceptor explicitly permits these paths, allowing requests to proceed without authentication or authorization checks

Why this happens

The underlying flaw is an authorization design error in which sensitive data-fetching endpoints are treated as publicly accessible by an authentication bypass or whitelist rule. This maps to CWE-284: Improper Access Control, because the application does not consistently enforce the required security policy before returning managed configuration data. The insecure pattern is allowing route-level exceptions to override the protection expected for sensitive resources.

Potential impact

  • Attackers may retrieve configuration items and files without authentication
  • Exposed credentials or tokens could enable access to connected services
  • Internal endpoints, infrastructure details, and deployment settings could be disclosed
  • The leaked information could support follow-on attacks, lateral movement, or data tampering
  • Organizations may experience confidentiality, integrity, or availability impacts if disclosed secrets are reused

General mitigation guidance

Mitigation generally focuses on making authentication and authorization mandatory for sensitive configuration APIs.

Common defensive patterns include:

  • Removing public route exceptions for configuration-fetching endpoints
  • Enforcing authentication and resource-level authorization before returning configuration data
  • Applying least-privilege access so users and services receive only the configuration they require
  • Reducing sensitive values stored in centralized configuration where practical
  • Separating secrets from ordinary configuration and using dedicated secret-management controls
  • Applying network segmentation, gateway policy, and deny-by-default access controls
  • Avoiding detailed configuration responses when a caller does not need the complete value

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis and route audits that flag sensitive endpoints excluded from authentication middleware
  • Code review checks for permissive interceptor, filter, gateway, or allowlist rules
  • Integration tests that verify anonymous requests receive denial responses for every configuration API
  • API inventory reviews comparing sensitive resources with enforced authentication and authorization policies
  • Web application monitoring for unauthenticated requests and unusual bulk reads of configuration endpoints
  • Automated security testing and policy checks in CI pipelines to detect access-control regressions

Sources

SourceLink
github.comgithub.com/fangtang7/CVE/blob/main/disconf/Unauthenticated.md

Frequently asked

questions

Yes, when the disconf service is reachable by an attacker. The exposed routes may be queried without authentication, subject to network controls and deployment exposure.

No authenticated account is expected to be necessary for the affected endpoints because the login interceptor permits those paths. Network access to the service remains necessary.

Require authentication and fine-grained authorization for every configuration-fetching endpoint, using a deny-by-default policy rather than public route allowlists.

Maintain an inventory of sensitive APIs, test anonymous and low-privilege access in CI, review middleware exceptions carefully, and monitor configuration reads for abnormal volume or scope.

Find out what's already
exploitable in your codebase.