Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-75338 – Unauthenticated Access to Configuration Data (Authentication Bypass) – Disconf 2.6.

Be the first to know when new zero-days emerge:

Summary

CVE-2026-75338 is an improper access control vulnerability (CWE-284) in Disconf, an open-source distributed configuration management platform, version 2.6.36. Several configuration-fetching API endpoints are explicitly whitelisted in the application’s login interceptor, allowing unauthenticated remote attackers to retrieve all stored configuration items and configuration files, including embedded plaintext credentials. The flaw carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: the LoginInterceptor component whitelists the paths /api/config/item, /api/config/file, /api/config/list, and /api/config/simple/list in its "do not intercept" path list, so requests to these endpoints bypass the platform’s authentication checks entirely.
  • Trigger condition: a simple unauthenticated HTTP GET request to any of the four endpoints (e.g., /api/config/list?app=<name>&env=<env>&version=<version>) returns configuration data without any credential or session token.
  • Attack vector: Network — no privileges and no user interaction are required (AV:N/AC:L/PR:N/UI:N).
  • Impact: full disclosure of configuration items and configuration files, which can include database passwords, Redis credentials, API keys, and other connection-string secrets stored in plaintext by the config center. Confidentiality, integrity, and availability impacts are all rated High under the CVSS vector, reflecting the potential for these disclosed credentials to enable further compromise of downstream systems.

Affected software

  • Disconf (distributed configuration management platform), version 2.6.36

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: No vendor-supplied patched version has been identified in the CVE record; check with the Disconf project/maintainers for an updated release that removes the four affected paths from the authentication bypass list.
  • If no patch is available:
    • Restrict network access to the Disconf config-center endpoints (/api/config/item, /api/config/file, /api/config/list, /api/config/simple/list) to trusted internal hosts only, using firewall rules, network segmentation, or a reverse proxy that enforces authentication.
    • Do not expose Disconf management interfaces directly to the internet.
    • Rotate any credentials (database passwords, Redis credentials, API keys) that may have been stored in Disconf configuration items or files, since they should be considered potentially exposed.
    • Monitor access logs for requests to the affected endpoints from unexpected or external IP addresses.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Disconf - 分布式配置管理平台, Disconf (within a zu-top-nav-link element)

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge