VulnerabilityPublished 20 Nov 2025Updated 21 Nov 2025

CVE-2025-61138: Insertion of Sensitive Information into Externally-Accessible File or Directory

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% 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:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Nov 2025
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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Immediately restrict access to the /dev-hub/ directory by configuring web server permissions to deny unauthenticated or unauthorized requests.
Implement network segmentation and firewall rules to limit external access to Qlik Sense Enterprise management interfaces and development hubs.
Monitor web server logs and network traffic for unusual access patterns targeting the /dev-hub/ path.
Employ web application firewalls (WAFs) with custom rules to block requests attempting to enumerate or access sensitive directories.
Review and harden Qlik Sense Enterprise configuration settings to disable unnecessary directory listings or developer features in production environments.
Engage with Qlik support or vendors to obtain patches or official remediation guidance as soon as they become available.
Conduct internal audits of data exposed via the /dev-hub/ directory to assess the scope of potential leakage and inform incident response plans.
Educate IT and security teams about the vulnerability and ensure rapid response capabilities for any detected exploitation attempts.

Description

Qlik Sense Enterprise v14.212.13 was discovered to contain an information leak via the /dev-hub/ directory.

Impact

For European organizations, the impact of CVE-2025-61138 is primarily the unauthorized disclosure of sensitive business intelligence and potentially personal data. This can lead to competitive disadvantage, regulatory non-compliance (notably GDPR), reputational damage, and potential legal liabilities. Since Qlik Sense Enterprise is used extensively across sectors such as finance, manufacturing, and public administration in Europe, the exposure of confidential dashboards, reports, or underlying data sources could have severe consequences. The vulnerability does not affect system integrity or availability, so operational disruption is unlikely; however, the confidentiality breach alone is critical. The ease of exploitation without authentication increases the risk of widespread scanning and data harvesting by threat actors. Organizations handling sensitive or regulated data are particularly at risk, as data leakage could trigger regulatory investigations and fines under GDPR. The lack of known exploits in the wild currently provides a window for mitigation, but the threat landscape could rapidly evolve.

CWE-538Insertion of Sensitive Information into Externally-Accessible File or Directory (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information.
Architecture and Design · Operation · System Configuration
Do not expose file and directory information to the user.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
WSDL Scanning (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

gist.github.com/Israel0x00/8a81ec98162e9ca8e4a3a6c8b4ef4762 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 27 Nov 2025, 22:09 UTC

WeaknessesCWE-538

Technical details

References

Community reviews

Related threats