CVE-2025-14808VulnerabilityPublished 25 Mar 2026

CVE-2025-14808: IBM InfoSphere Information Server · Use of GET Request Method With Sensitive Query Strings

Affects IBM InfoSphere Information ServerSource CVE Database V5

Not known to be exploited · CVSS 3.1 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

3.1Low

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: Low
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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 25 Mar 2026
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
IBMInfoSphere Information Server	Affected >=11.7.0.0 <=11.7.1.6	Fixed in–

CPE configurations (2)

cpe:2.3:a:ibm:infosphere_information_server:11.7.0.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:infosphere_information_server:11.7.1.6:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2025-14808, organizations should immediately avoid transmitting sensitive information in HTTP GET query strings within IBM InfoSphere Information Server workflows. Instead, sensitive data should be sent using HTTP POST requests or other secure methods that do not expose data in URLs. Enforce the use of HTTPS with strong TLS configurations to protect data in transit and prevent interception by MitM attackers. Network segmentation and monitoring can help detect and prevent unauthorized network access. Organizations should monitor IBM’s security advisories for patches or configuration updates addressing this vulnerability and apply them promptly once available. Additionally, review and audit application logs and proxy configurations to ensure sensitive data is not inadvertently logged or exposed. Educate developers and administrators on secure coding and data handling practices to prevent similar issues. Finally, consider deploying network security tools such as intrusion detection systems (IDS) to identify suspicious traffic patterns indicative of MitM attacks.

Description

IBM InfoSphere Information Server 11.7.0.0 through 11.7.1.6 could allow an attacker to obtain sensitive information from the query string of an HTTP GET method to process a request which could be obtained using man in the middle techniques.

Impact

The primary impact of this vulnerability is the potential unauthorized disclosure of sensitive information transmitted via HTTP GET query strings. If exploited, attackers could obtain confidential data such as session tokens, credentials, or other sensitive parameters, which could facilitate further attacks or unauthorized access. However, the impact is limited by the requirement for the attacker to intercept network traffic, which is more feasible in unencrypted or poorly secured network environments. The vulnerability does not allow modification or disruption of data or services, so integrity and availability remain unaffected. Organizations using IBM InfoSphere Information Server in environments where network traffic is not fully encrypted or where MitM attacks are plausible face increased risk. This could be particularly concerning in industries handling sensitive data such as finance, healthcare, or government sectors. The low CVSS score indicates a relatively low risk compared to more severe vulnerabilities, but the exposure of sensitive information can still have compliance and reputational consequences.

Summary

CVE-2025-14808 identifies a security weakness in IBM InfoSphere Information Server versions 11.7.0.0 through 11.7.1.6 related to the use of HTTP GET requests to transmit sensitive query strings. The core issue is that sensitive information, such as authentication tokens or confidential parameters, is included in the URL query string of GET requests. Since URLs are often logged by servers, proxies, and browsers, and are more susceptible to interception during transmission, this practice exposes sensitive data to potential attackers. Specifically, an attacker positioned to perform man-in-the-middle (MitM) attacks on the network can capture these GET requests and extract sensitive information from the query strings. The vulnerability does not affect the integrity or availability of the system but compromises confidentiality to a limited extent. The attack complexity is high because the attacker must be able to intercept network traffic, and the attacker requires low privileges and no user interaction. The CVSS vector (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N) reflects these factors, resulting in a low overall score of 3.1. No public exploits have been reported, and IBM has not yet provided patches, but the vulnerability is publicly disclosed and should be addressed proactively.

CWE-598Use of HTTP Request With Sensitive Query String (opens in a new tab)
Variant weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The web application uses an HTTP method to process a request, but the request includes sensitive information in the query string.
Implementation
When sending sensitive information, only include it in the request body or request headers instead of the query string. This may require avoiding use of GET requests.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Web Service Security (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V3.1.1 (opens in a new tab)
V13.1.3 (opens in a new tab)
V8.3.4 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (2)

Description

AI analysisMachine-generated, updated 25 Mar 2026, 20:49 UTC

WeaknessesCWE-598

Technical details

References

Community reviews

Related threats