Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach Platform RTM web interface
-
ExploitSubmit crafted SQL in request parameter
-
ExecutionInjection executes in back-end DB
-
ImpactRead/modify/delete monitoring data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network access to the IBM Platform RTM web/reporting interface and a request parameter that flows unsanitized into a back-end SQL query. The vendor vector indicates PR:N/UI:N (no authentication or user interaction), so against an exposed default deployment a remote attacker could exploit it directly; however, Platform RTM is typically deployed inside HPC/LSF cluster management networks rather than internet-facing, which is the primary real-world limiting factor. The description does not name the specific vulnerable parameter or page, and it does not confirm whether the endpoint sits behind a login, so verify authentication placement against the IBM advisory before assuming fully pre-auth reachability. |
| Impact | The vendor CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L, 8.6 HIGH) describes a network-reachable, low-complexity, unauthenticated SQL injection - a genuinely serious combination on paper. However, no EPSS score, no CISA KEV listing, and no public POC were provided, so the current status is 'no public exploit identified at time of analysis.' There is no SSVC data supplied. The high-CVSS signal is therefore not corroborated by any real-world exploitation evidence, and the true priority is tempered by the affected product's very narrow deployment footprint (IBM Platform RTM, an HPC/Spectrum LSF cluster-monitoring dashboard). One internal inconsistency is worth flagging: the description says an attacker could 'view, add, modify, or delete information in the back-end database' - a full read/write compromise that would normally justify C:H/I:H, yet the vendor rated integrity and availability only Low (I:L/A:L); the impact metrics appear understated relative to the described capability. Also note PR:N (unauthenticated) is asserted by the vendor vector but the description does not itself state whether the injectable endpoint is pre- or post-authentication - verify with the IBM advisory. Net: real and patch-worthy for the small population running Platform RTM, but not a broad emergency given niche prevalence and absence of exploitation signals. |
| Exploit ScenarioDerived | A remote attacker who can reach the IBM Platform RTM web interface submits a request containing a crafted SQL fragment in a vulnerable parameter, which is concatenated into a back-end query. Per the CVSS vector this requires no authentication and low complexity, letting the attacker read sensitive cluster/monitoring data and add, alter, or delete database records. No public exploit code or active exploitation has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 18, 2026
Unauthenticated SQL injection in IBM Platform RTM (the real-time monitoring component of Spectrum LSF) lets a remote attacker who can reach the product's web/reporting interface inject crafted SQL into a back-end database, reading, adding, modifying, or deleting data. The vendor rates it CVSS 3.1 8.6 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L), and our independent assessment agrees on severity while noting that in typical HPC/LSF deployments the component sits on a trusted cluster-management network rather than the public internet, which is the main real-world brake on exploitation; the assessed vector also raises the integrity impact to H (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L) because successful SQL injection against a writable application account commonly yields full row-level manipulation, not just partial. No public exploit code was identified at time of analysis and the flaw is not in CISA KEV, though the PR:N/UI:N profile means no credentials or user interaction are needed once the endpoint is reachable. Vendor patch availability is listed as available, giving administrators a direct fix path; the specific vulnerable parameter and page are not named in available data, so pre-auth reachability should be verified against the IBM advisory.
RemediationAI
Patch availability is confirmed by the vendor: apply the fix from IBM's advisory at https://www.ibm.com/support/pages/node/7287769, which is the authoritative source for the exact fixed build of IBM Platform RTM/Spectrum LSF - the input data does not provide a specific fix version number, so do not assume one and verify against that page before upgrading. If immediate patching is not possible, the highest-value compensating control is network segmentation: keep the Platform RTM web/reporting interface on the internal HPC/LSF management network and block inbound access from user subnets and the internet, which eliminates the AV:N reachability the exploit depends on (trade-off: administrators lose out-of-band monitoring access and must use jump hosts or VPN). Second, since the assessed vector is PR:N/UI:N, place the interface behind an authenticating reverse proxy or restrict it to authenticated administrative accounts at the network layer, accepting that this is a compensating control rather than a fix for the underlying injection. Third, run the Platform RTM database account with least privilege - read-only where the reporting function permits, and no DDL or broad write grants - so an injected statement cannot modify or delete data (trade-off: some reporting features may need temporary elevated grants). Finally, a WAF or reverse proxy with SQL-injection signatures can filter obvious payloads but is bypassable and should only buy time until the vendor patch is applied.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-89, improper neutralization of special elements used in an SQL command, in IBM Platform RTM, the monitoring and reporting layer distributed with IBM Spectrum LSF. According to the CPE data (cpe:2.3:a:ibm:spectrum-lsf_:_ibm_platform_rtm:*:*:*:*:*:*:*:*) the affected component is the Platform RTM piece of the Spectrum LSF product family, with all versions matched by the wildcard, so administrators should treat any deployed Platform RTM instance as potentially affected until the vendor advisory is checked. Functionally, a request parameter (page, report, or filter field in the web/reporting UI) is passed into a back-end SQL query without adequate parameterization, allowing injected SQL to alter the query's logic. Because the query runs with the application's database privileges, the attacker's reach is bounded by those privileges: strong read/write access enables data disclosure and modification, while a least-privileged account constrains the damage. The technology stack is a Java/WebSphere-style enterprise reporting front end over a relational back-end database, typically reachable only from the HPC management network where LSF masters carry the scheduler's resource and job telemetry.
Know when Spectrum Lsf gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
Network, low-complexity, unauthenticated per vendor; description's view+add+modify+delete justifies C:H and I:H (higher than vendor I:L), with A:L for data deletion rather than full service outage.
Primary rating from Vendor (ibm).
CVSS VectorVendor: ibm
DescriptionCVE.org
IBM Platform RTM is 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.
Executive ViewAI
IBM Platform RTM, the real-time monitoring web/reporting component of Spectrum LSF, carries an unauthenticated SQL injection flaw (CVE-2026-17619) that allows anyone who can reach that interface to read, alter, or delete data in its back-end database. Because Platform RTM typically sits on trusted cluster-management networks used by HPC operations teams, the primary exposure is to insiders, compromised hosts, or any workload that can route to the reporting interface - a foothold there could corrupt monitoring, reporting, and scheduling data that engineering and research groups rely on. A vendor patch is available, so leadership should treat this as a scheduled-but-prioritized remediation item rather than an emergency, with network reachability of the reporting port as the key risk dial.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Spectrum Lsf
View allIBM Platform LSF 10.1 contains an unspecified vulnerability that could allow a local user to escalate their privileges a
IBM Platform LSF 9.1 and 10.1, IBM Spectrum LSF Suite 10.2, and IBM Spectrum Suite for HPA 10.2 could allow a local user
IBM Spectrum LSF 9.1.1 9.1.2, 9.1.3, and 10.1 could allow a local user to change their job user at job submission time d
EUVD-2026-83297
GHSA-7mfh-r2p9-v6hc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB