CVE-2025-36173: IBM InfoSphere Data Architect · Cross-site Scripting
Affects IBM InfoSphere Data ArchitectSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMInfoSphere Data Architect | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:ibm:infosphere_data_architect:9.2.1:*:*:*:*:*:*:*
AI-suggested
- Apply strict input validation and output encoding on all user-supplied data within IBM InfoSphere Data Architect interfaces to prevent script injection.
- Deploy and configure web application firewalls (WAFs) with rules targeting common XSS attack patterns to provide an additional layer of defense.
- Educate users about the risks of interacting with suspicious links or content, emphasizing caution to reduce successful exploitation via social engineering.
- Monitor application logs and network traffic for unusual activity indicative of attempted XSS attacks.
- Segregate and limit user privileges within the application to minimize potential damage from compromised accounts.
- Regularly check IBM security advisories for patches or updates addressing this vulnerability and apply them promptly once available.
- Consider implementing Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in the application context.
- Conduct security assessments and penetration testing focused on web interface input handling to identify and remediate similar issues proactively.
Description
Affected Product(s)Version(s)InfoSphere Data Architect9.2.1