Skip to main content
VulnerabilityPublished

CVE-2026-17111: IBM i · SQL Injection

Affects IBM iSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.6 High.

Data as of 11 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% 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:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 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 11 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
IBMAffected
  • 7.3 – 7.6
4 affected builds
Fixed in–
Mavenibm/ipkg:maven/ibm/iOther threatsAffected
  • 7.3 – 7.6
4 affected builds
Fixed in–

CPE configurations (8)

  • cpe:2.3:a:ibm:i:7.6:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:i:7.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:i:7.5:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:i:7.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:i:7.4:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:i:7.4.0:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official fix is released, organizations should apply standard SQL injection mitigations such as input validation and parameterized queries where possible. Monitor vendor communications for updates on patches or official workarounds.

Description

IBM i 7.6, 7.5, 7.4, and 7.3 s vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or delete information in the back-end database.

References

Community reviews

Loading reviews…