CVE-2025-0154VulnerabilityPublished 2 Apr 2025Updated 1 Sep 2025

CVE-2025-0154: IBM TXSeries for Multiplatforms · Improper Neutralization of HTTP Headers for Scripting Syntax

Affects IBM TXSeries for MultiplatformsSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 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 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Apr 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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

Affected software

Product	Affected	Fixed in
IBM TXSeries for Multiplatforms	Affected =9.1 =11.1	Fixed in–

AI-suggested

2) Implement strict input validation and sanitization at the application and middleware layers to ensure HTTP headers are properly neutralized and do not contain malicious scripting syntax. 3) Employ Web Application Firewalls (WAFs) configured to detect and block anomalous or suspicious HTTP header manipulations that could exploit this vulnerability. 4) Conduct thorough security testing and code reviews focusing on HTTP header handling within applications that interface with TXSeries. 5) Monitor network traffic for unusual patterns or attempts to exploit header-based vulnerabilities. 6) Restrict exposure of TXSeries interfaces to trusted networks and use network segmentation to limit potential attack surfaces. 7) Educate development and operations teams about secure coding practices related to HTTP headers and middleware security. These measures, combined with vigilant monitoring and incident response preparedness, will reduce the risk posed by this vulnerability beyond generic patching advice.

Description

IBM TXSeries for Multiplatforms 9.1 and 11.1 could disclose sensitive information to a remote attacker due to improper neutralization of HTTP headers.

Impact

For European organizations, the disclosure of sensitive information through this vulnerability could have significant repercussions, especially for industries relying on IBM TXSeries for critical transaction processing, such as banking, insurance, manufacturing, and government services. Exposure of sensitive data may lead to breaches of data protection regulations like the GDPR, resulting in legal penalties and reputational damage. Additionally, leaked information could be used by threat actors to facilitate more advanced attacks, including targeted intrusions or lateral movement within networks. The medium severity rating reflects that while the vulnerability does not directly compromise system integrity or availability, the confidentiality breach alone can have cascading effects on organizational security posture. Organizations handling personal data or critical business transactions are particularly at risk, as attackers could gain insights into internal systems or user information. The fact that no authentication or user interaction is required increases the risk of automated exploitation attempts, although no known exploits have been reported yet.

CWE-644Improper Neutralization of HTTP Headers for Scripting Syntax (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes web scripting syntax in HTTP headers that can be used by web browser components that can process raw headers, such as Flash.
Architecture and Design
Perform output validation in order to filter/escape/encode unsafe data that is being passed from the server in an HTTP response header.
Architecture and Design
Disable script execution functionality in the clients' browser.
OWASP Cheat Sheets
Content Security Policy (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
Query Parameterization (opens in a new tab)
OWASP ASVS 4.0.3
V14.4.6 (opens in a new tab)
V14.4.4 (opens in a new tab)
V14.4.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7229880 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Sep 2025, 01:49 UTC

WeaknessesCWE-644

Technical details

References

Community reviews

Related threats