CVE Intelligence
CISA KEV Critical Injection

CVE-2023-48365 — Qlik Sense HTTP Tunneling Vulnerability

Qlik Sense Enterprise for Windows before August 2023 Patch 2 allows unauthenticated remote code execution, aka QB-21683. Due to improper validation of HTTP headers, a remote attacker is able to elevate their privilege by tunneling HTTP requests, allowing them to execute HTTP requests on the backend server that hosts the repository application. The fixed versions 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. NOTE: this issue exists because of an incomplete fix for CVE-2023-41265.

Published Nov 15, 2023 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: mitre

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

CISA KEV · Jan 13, 2025 R used by ransomware (CISA)
How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Used in ransomware campaigns (CISA)+10
  • EPSS 47.5% (30-day exploitation probability)+15
  • Technical severity (critical)+10

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Jan 13, 2025
EPSS FIRST
47.45%
ahead of 99% of scored CVEs · Oct 15, 2026
Affects
Qlik
Qlik Sense
CVSS base
9.9
Critical · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

CISA required action CISA

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

US federal deadline: Feb 3, 2025 — passed 620 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Qlik Qlik Sense).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. EPSS ahead of 99% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Qlik Qlik Sense version may_2023version november_2021-patch_13version november_2021-patch_12version november_2021-patch_11version november_2021-patch_10version november_2021-patch_1version november_2021version may_2023-patch_5
and 84 more version may_2023-patch_4version may_2023-patch_3version may_2023-patch_2version may_2023-patch_1version november_2021-patch_14version may_2022-patch_9version may_2022-patch_8version may_2022-patch_7version may_2022-patch_6version may_2022-patch_5version may_2022-patch_4version may_2022-patch_3version may_2022-patch_2version may_2022-patch_15version may_2022-patch_14version november_2022version november_2022-patch_9version november_2022-patch_8version november_2022-patch_7version november_2022-patch_6version november_2022-patch_5version november_2022-patch_4version november_2022-patch_3version november_2022-patch_2version november_2022-patch_11version november_2022-patch_10version november_2022-patch_1version may_2022-patch_13version november_2021-patch_9version november_2021-patch_8version november_2021-patch_7version november_2021-patch_6version november_2021-patch_5version november_2021-patch_4version november_2021-patch_3version november_2021-patch_2version november_2021-patch_16version november_2021-patch_15version august_2022-patch_7version february_2022-patch_14version february_2022-patch_13version february_2022-patch_12version february_2022-patch_11version february_2022-patch_10version february_2022-patch_1version february_2022version august_2023-patch_1version august_2023version august_2022-patch_9version august_2022-patch_8version february_2022-patch_2version august_2022-patch_6version august_2022-patch_5version august_2022-patch_4version august_2022-patch_3version august_2022-patch_2version august_2022-patch_13version august_2022-patch_12version august_2022-patch_11version august_2022-patch_10version august_2022-patch_1version february_2023-patch_3version may_2022-patch_12version may_2022-patch_11version may_2022-patch_10version may_2022-patch_1version may_2022version february_2023-patch_9version february_2023-patch_8version february_2023-patch_7version february_2023-patch_6version february_2023-patch_5version february_2023-patch_4version august_2022version february_2023-patch_2version february_2023-patch_1version february_2023version february_2022-patch_9version february_2022-patch_8version february_2022-patch_7version february_2022-patch_6version february_2022-patch_5version february_2022-patch_4version february_2022-patch_3
Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.9 CVSS 3.1 Critical 3.1 6.0 nvd@nist.gov via NIST National Vulnerability Database
9.6 CVSS 3.1 Critical 3.1 5.8 cve@mitre.org via NIST National Vulnerability Database
9.6 CVSS 3.1 Critical — — GitHub, Inc. via GitHub Security Advisories
9.6 CVSS 3.1 Critical — — mitre via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 9.9 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-444 · HTTP Request Smuggling

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Jan 13, 2025
Federal deadline
Feb 3, 2025
passed 620 day(s) ago
Ransomware use
Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

EPSS over time FIRST

Oct 12, 2026 → Oct 15, 2026 · 4 reading(s) · max 47.45%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
  • Hunt retroactively in logs from before Jan 13, 2025 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Affected products added · qlik/qlik sense
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 9.9
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2025
  • Added to CISA KEV catalog
    Jan 12, 2025 · CISA
  • 2023
  • CVE published
    Nov 15, 2023 · mitre

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

4 on the record

Elsewhere on this site

Qlik
every CVE for this vendor
2025-01
what else CISA listed that month
Injection
same class
CWE-444
other pages naming this weakness

Related CVEs (same products)

  • CVE-2025-61138 Qlik Sense Enterprise v14.212.13 was discovered to contain an information leak via the… Nov 20, 2025
  • CVE-2023-41265 Qlik Sense HTTP Tunneling Vulnerability KEV Aug 29, 2023
  • CVE-2023-41266 Qlik Sense Path Traversal Vulnerability KEV Aug 29, 2023

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2023-48365 is "Qlik Sense HTTP Tunneling Vulnerability", rated Critical. It affects Qlik Sense (Qlik); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 9.9 describes technical severity. EPSS 47.45% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.