Description
disconf (Distributed Configuration Management Platform) 2.6.36 is vulnerable to Incorrect Access Control. The config-fetching APIs /api/config/item, /api/config/file, /api/config/list and /api/config/simple/list are exposed without authentication. The LoginInterceptor explicitly whitelists these four paths, so any anonymous attacker can read every configuration item and configuration file managed by the config center.
Published: 2026-08-26
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

disconf (Distributed Configuration Management Platform) 2.6.36 contains an Incorrect Access Control flaw that allows any unauthenticated user to call the /api/config/item, /api/config/file, /api/config/list, and /api/config/simple/list endpoints. This flaw results in full read access to every configuration item and configuration file stored by the platform, potentially exposing sensitive data such as credentials, secrets, and system settings. The underlying weakness is an overly permissive whitelist that bypasses authentication checks, leading to a classic Unauthorized Read scenario.

Affected Systems

The affected product is disconf version 2.6.36, a distributed configuration management platform used to centralize configuration for various services. No vendor name is specified, so the platform should be identified by its upstream project source. Any deployment running exactly this version is vulnerable.

Risk and Exploitability

While no CVSS score is listed, the lack of authentication on configuration endpoints means a remote attacker can read arbitrary configuration data from the network. The EPSS score is not available, and the vulnerability is not in the CISA KEV catalog, but the exposed data can enable credential theft, privilege escalation, or further network pivoting. The attack vector is inferred to be remote over the network via HTTP, as the APIs are publicly reachable and do not require any authentication token.

Generated by OpenCVE AI on August 27, 2026 at 00:25 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade disconf to the latest release that removes the whitelist from the login interceptor
  • Configure the platform’s authentication middleware to require a valid session token for all /api/config/* paths
  • Implement IP‑based or role‑based access control on the reverse proxy or API gateway
  • If upgrading immediately is not possible, block external traffic to the four vulnerable endpoints using firewall or reverse‑proxy rules

Generated by OpenCVE AI on August 27, 2026 at 00:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 27 Aug 2026 00:45:00 +0000

Type Values Removed Values Added
Title Unauthorized Access to Configuration Data in disconf 2.6.36
Weaknesses CWE-284

Wed, 26 Aug 2026 23:15:00 +0000

Type Values Removed Values Added
Description disconf (Distributed Configuration Management Platform) 2.6.36 is vulnerable to Incorrect Access Control. The config-fetching APIs /api/config/item, /api/config/file, /api/config/list and /api/config/simple/list are exposed without authentication. The LoginInterceptor explicitly whitelists these four paths, so any anonymous attacker can read every configuration item and configuration file managed by the config center.
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2026-08-26T22:11:07.314Z

Reserved: 2026-08-17T00:00:00.000Z

Link: CVE-2026-75338

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-26T23:17:18.903

Modified: 2026-08-26T23:17:18.903

Link: CVE-2026-75338

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-27T00:30:14Z

Weaknesses