Skip to main content
Mallory
CriticalExploited in the wildCISA KEVVulnerability

CVE-2023-48365: DoubleQlik

Published Nov 15, 2023 · Updated 6 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS9.9Critical · v3.1
EPSS47.7%99th percentile
CISA KEVYesAdded Jan 13, 2025
In the wildActivePer CISA KEV
Vendor
Qlik
IdentifiersCVE-2023-48365CWE-444 · Inconsistent Interpretation of…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
QlikQlik Senseapplication
FAQ

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.
Activity feed

Recent activity

17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
the hacker newsNews · Nov 11, 2026Hackers Target Qlik Sense Servers With Reverse Shells, Stage ActiveMQ and Veeam ExploitsAn unauthenticated remote code execution vulnerability in Qlik Sense Enterprise for Windows caused by improper HTTP header validation, enabling privilege escalation and tunneled backend HTTP requests. The article describes it as arising from an incomplete fix for CVE-2023-41265 and links it to the November 2023 CACTUS ransomware campaign. Its use in the October 2026 activity is not established.Read more ↗nuclei templates pull requestsNews · Mar 26, 2026Add 5 KEV CVE templates (Fortinet, SonicWall, Qlik Sense) by ElromEvedElElyon · Pull Request #15698 · projectdiscovery/nuclei-templates · GitHubA remote code execution vulnerability in Qlik Sense Enterprise involving HTTP tunneling.Read more ↗greynoise blogNews · Feb 2, 2026The Noise in the Silence: Unmasking CISA's Hidden KEV Ransomware UpdatesA Qlik vulnerability that CISA KEV’s knownRansomwareCampaignUse field silently flipped to Known during 2025 (evidence of ransomware campaign use).Read more ↗northwaveNews · Jan 1, 2026PrickSense How Cactus exploits Qlik SenseA bypass of an incomplete mitigation for the Qlik Sense vulnerabilities, known as DoubleQlik. The article identifies ZeroQlik and/or DoubleQlik exploitation as the initial-access mechanism in Cactus ransomware incidents, enabling arbitrary commands under the Qlik Sense service account. Attribution to this specific CVE remains uncertain because the available logs cannot distinguish the exploit routes.Read more ↗
+11 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence4Every report linking this CVE to a named adversary.
Associated malware14Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.