CVE-2026-75338: disconf · Improper Access Control
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Until a fix is available, restrict network access to the vulnerable API endpoints to trusted users only, or implement additional access controls at the network or application layer to prevent anonymous access.
Description
disconf 2.6.36 has an incorrect access control vulnerability where certain config-fetching API endpoints are accessible without authentication. This allows any anonymous attacker to read all configuration items and files managed by the config center. The vulnerability affects the /api/config/item, /api/config/file, /api/config/list, and /api/config/simple/list endpoints due to explicit whitelisting in the LoginInterceptor. The CVSS score is 9.8, indicating a critical severity level.