I vulnerabilitiesRanked by how likely they are to be used.
I is made by IBM. We track 96 published vulnerabilities listed under that exact name, across 7 versions. None of them is on the list of flaws known to be exploited today. IBM lists newer releases under their own names, such as I Access, so check those pages too.
We keep watching the known-exploited list.
Is I listed under other names? Yes.
IBM also lists I under more specific names, such as I Access and I Access Client Solutions. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which I vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of I's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which I flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 13%CVE-2025-36038Critical
IBM WebSphere Application Server 8.5 and 9.0 could allow a remote attacker to execute arbitrary code on the system with a specially crafted sequence of serialized objects.
- 5.2%CVE-2019-4728High
IBM Sterling B2B Integrator Standard Edition 5.2.0.0 through 5.2.6.5_2, 6.0.0.0 through 6.0.3.2, and 6.1.0.0 could allow a remote attacker to execute arbitrary code on the system, caused by the deserialization of...
- 4.8%CVE-2020-4949High
IBM WebSphere Application Server 7.0, 8.0, 8.5, and 9.0 is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data.
- 4.1%CVE-2021-20354High
IBM WebSphere Application Server 8.0, 8.5, and 9.0 could allow a remote attacker to traverse directories.
- 3.5%CVE-2013-5385High
The OSPF implementation in IBM i 6.1 and 7.1, in z/OS on zSeries servers, and in Networking Operating System (aka NOS, formerly BLADE Operating System) does not properly validate Link State Advertisement (LSA) type 1...
- 2.3%CVE-2020-9412Critical
The file transfer component of TIBCO Software Inc.'s TIBCO Managed File Transfer Platform Server for IBM i contains a vulnerability that theoretically allows execution of arbitrary commands at the privilege level of...
- 2.2%CVE-2022-22495High
IBM i 7.3, 7.4, and 7.5 is vulnerable to SQL injection.
- 1.9%CVE-2023-23477Critical
IBM WebSphere Application Server 8.5 and 9.0 traditional could allow a remote attacker to execute arbitrary code on the system with a specially crafted sequence of serialized objects.
- 1.7%CVE-2020-4870High
IBM MQ 9.2 CD and LTS are vulnerable to a denial of service attack caused by an error processing connecting applications.
Running I? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
XMLscanner.java in Apache Xerces2 Java Parser before 2.12.0, as used in the Java Runtime Environment (JRE) in IBM Java 5.0 before 5.0 SR16-FP3, 6 before 6 SR14, 6.0.1 before 6.0.1 SR6, and 7 before 7 SR5 as well as Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, JRockit R28.2.8 and earlier, JRockit R27.7.6 and earlier, Java SE Embedded 7u40 and earlier, and possibly other products allows remote attackers to cause a denial of service via vectors related to XML attribute names.
- Matched to
- I on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 96 published vulnerabilities listed under the name I, across 7 versions.
None of I's vulnerabilities is on the list of flaws known to be exploited today.
IBM also lists I under more specific names, such as I Access and I Access Client Solutions. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track I. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.