VulnerabilityPublished 21 Sep 2026Updated 14 Oct 2026

CVE-2026-94216: ST Engineering iDirect iDX · HTTP Response Splitting

Affects ST Engineering iDirect iDXSource CVE Database V5

Public exploit available · CVSS 5.3 Medium · end of life, no fix coming : replace or isolate ST Engineering iDirect iDX; no fix will be released.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: None coming – the product is end of life

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

No fix will be released: ST Engineering iDirect iDX is end of life. Replace it, or isolate it from untrusted networks until you can.

Affected software

Product	Affected	Fixed in
ST Engineering iDirectiDX	Affected =n/a	Fixed in–
ST Engineering iDirectEvo iDX	Affected =n/a	Fixed in–

CPE configurations (2)

cpe:2.3:a:st_engineering_idirect:idx:*:*:*:*:*:*:*:*
cpe:2.3:a:st_engineering_idirect:evo_idx:*:*:*:*:*:*:*:*

AI-suggested

Users should upgrade to supported versions (X10, X11, Velocity 5.x+) which have no validated evidence of this vulnerability. If upgrading is not possible, consider implementing network-level protections such as web application firewalls to detect and block malicious HTTP requests targeting the Success argument. Monitor vendor advisories for any future updates.

Description

CVE-2026-94216 is a medium severity HTTP response splitting vulnerability in ST Engineering iDirect iDX and Evo iDX affecting the /authorize HTTP Request Handler component. It allows remote attackers to manipulate the Success argument to perform HTTP response splitting. The vulnerability affects only end-of-life (EOL) versions such as X7 and some legacy Evolution 21.x models. Current supported releases (X10, X11, Velocity 5.x+) have no confirmed impact. No patch or remediation is available since the affected products are no longer supported.

Impact

An attacker can remotely exploit this vulnerability to perform HTTP response splitting, which may enable attacks such as web cache poisoning or cross-user attacks. However, the impact is limited to unsupported legacy versions of the product. Supported versions have no confirmed vulnerability. The CVSS 4.0 score is 5.3 (medium), reflecting network attack vector, low complexity, no privileges required, user interaction required, and limited impact on confidentiality and integrity.

Summary

This vulnerability in ST Engineering iDirect iDX and Evo iDX involves HTTP response splitting via manipulation of the Success argument in the /authorize HTTP Request Handler. The flaw allows remote attackers to craft malicious input that can split HTTP responses, potentially leading to web cache poisoning or cross-user attacks. The issue has been publicly disclosed and affects only unsupported legacy versions (EOL X7 and some Evolution 21.x). Supported versions have no validated evidence of being vulnerable.

References

Community reviews

Loading reviews…