Skip to content
major vulnerability· requires attention

Enterprise IBM product with remote SQLi allowing database compromise; widespread IBM usage makes this broadly relevant.

Applications

CVE-2026-17619

8.6
High
EPSS n/aSep 21, 2026

Remote SQL injection in IBM Platform RTM allowing unauthorized DB access and modification.

common questions

Is CVE-2026-17619 being exploited?

Not confirmed. CVE-2026-17619 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-17619?

CVE-2026-17619 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-17619?

Not known from our data. No patch reference has been recorded for CVE-2026-17619, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-17619 affect?

CVE-2026-17619 affects IBM Platform RTM. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-17619?

Apply vendor patch/mitigations ASAP; restrict access, audit logs, and validate inputs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
IBM Platform RTM
impact

Remote SQL injection enabling attackers to read, add, modify, or delete data in the back-end database.

action required

Immediate action required

affected versions
IBM spectrum-lsf : IBM Platform RTM
  • affected10.2.0.15,10.2.0.16

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free