Skip to main content
VulnerabilityPublished

CVE-2026-1014: IBM InfoSphere Information Server · Cleartext Transmission

Affects IBM InfoSphere Information ServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
IBMInfoSphere Information ServerAffected
  • >=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

  1. Monitor IBM’s official channels for patches or updates addressing CVE-2026-1014 and apply them promptly once available.
  2. Implement network segmentation and strict access controls to limit network access to IBM InfoSphere servers, reducing exposure to potential attackers.
  3. Employ encryption protocols such as TLS for all communications involving InfoSphere to prevent interception of cleartext JSON responses.
  4. Use network intrusion detection and prevention systems (IDS/IPS) to monitor and block suspicious activities targeting InfoSphere servers.
  5. Conduct regular security audits and traffic analysis to detect anomalous data transmissions that may indicate exploitation attempts.
  6. Enforce the principle of least privilege for accounts accessing InfoSphere to minimize the impact of compromised credentials.
  7. Educate internal teams about the risks of cleartext data transmission and encourage reporting of unusual network behavior.
  8. Consider deploying application-layer firewalls or API gateways that can inspect and sanitize JSON responses to prevent sensitive data leakage.

Description

IBM InfoSphere Information Server 11.7.0.0 through 11.7.1.6 is vulnerable to exposure of sensitive information via JSON server response manipulation.

References

Community reviews

Loading reviews…