What is the CVSS score of CVE-2025-61138?

CVE-2025-61138 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.1%.

Which versions of Qlik Sense are affected by CVE-2025-61138?

Organizations using Qlik Sense Enterprise v14.212.13 face notable risk from CVE-2025-61138 rated CVSS 7.5. Exploitation could compromise the security of affected deployments.

How to fix or mitigate CVE-2025-61138?

Within 30 days: Identify all affected systems and apply vendor patches as part of regular patch cycle. Monitor vendor channels for patch availability.

Qlik Sense CVE-2025-61138

HIGH

Insertion of Sensitive Information into Externally-Accessible File (CWE-538)

2025-11-20 cve@mitre.org

Information Disclosure Qlik Sense

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 19:23 vuln.today

CVE Published

Nov 20, 2025 - 22:16 nvd

HIGH 7.5

DescriptionCVE.org

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

AnalysisAI

Qlik Sense Enterprise v14.212.13 was discovered to contain an information leak via the /dev-hub/ directory. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-538. Qlik Sense Enterprise v14.212.13 was discovered to contain an information leak via the /dev-hub/ directory. Affected products include: Qlik Qlik Sense.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.