CVE-2023-48365: DoubleQlik
- Vendor
- Qlik
DoubleQlik (CVE-2023-48365), also tracked as QB-21683, is an unauthenticated HTTP request tunneling vulnerability in Qlik Sense Enterprise for Windows. Improper validation of HTTP headers allows a remote attacker to tunnel requests to the backend server hosting the repository application, execute privileged backend requests, and achieve arbitrary code execution with backend service permissions. The vulnerability bypasses an incomplete fix for CVE-2023-41265 and affects multiple release branches before their respective corrective patches.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can compromise the confidentiality and integrity of the Qlik Sense installation and permit takeover of the host within the privileges available to its backend services. This access can facilitate data theft, installation of remote-access tools, persistence, and subsequent lateral movement or ransomware deployment. Cactus ransomware campaigns have exploited Qlik Sense vulnerabilities for initial access, although investigators could not consistently distinguish DoubleQlik exploitation from exploitation of the CVE-2023-41266 and CVE-2023-41265 chain.
Mitigation
If you can’t patch tonight, do this now.
Until the corrective update is installed, remove direct Internet exposure and restrict Qlik Sense access to trusted networks and authorized administrators. Use network segmentation to limit access to backend services and constrain lateral movement from the Qlik Sense host. Monitor for unusual child processes launched by the Qlik Sense Scheduler service, unexpected remote-management software, and unauthorized persistence. These controls reduce exposure but do not replace patching.
Remediation
Patch, then assume compromise.
Upgrade to a supported release containing the fix. The minimum fixed versions for the listed branches are August 2023 Patch 2, May 2023 Patch 6, February 2023 Patch 10, November 2022 Patch 12, August 2022 Patch 14, May 2022 Patch 16, February 2022 Patch 15, and November 2021 Patch 17. Upgrade or replace end-of-support installations rather than retaining unsupported branches. Validate patch deployment with version checks and targeted vulnerability testing. The earlier fix for CVE-2023-41265 alone is insufficient. Investigate previously exposed installations for compromise, because patching does not remove attacker-established persistence.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2023-48365 exploited in the wild?
- Yes. As of Nov 11, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jan 13, 2025.
- Is there a public exploit for CVE-2023-48365?
- As of Nov 11, 2026, Mallory has found no public exploit for CVE-2023-48365.
- Is there a patch for CVE-2023-48365?
- Upgrade to a supported release containing the fix. The minimum fixed versions for the listed branches are August 2023 Patch 2, May 2023 Patch 6, February 2023 Patch 10, November 2022 Patch 12, August 2022 Patch 14, May 2022 Patch 16, February 2022 Patch 15, and November 2021 Patch 17.
- What products are affected by CVE-2023-48365?
- Qlik Sense.
- How severe is CVE-2023-48365?
- CVE-2023-48365 has a CVSS v3.1 score of 9.9 (Critical) and an EPSS score of 47.7% (99th percentile) as of Nov 11, 2026.
Recent activity
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.