Unauthenticated denial of service via infinite parsing
Published Oct 12, 2026 · Updated Oct 12, 2026
Parsing-loop DoS in IBM Maximo Application Suite IoT Component allows remote attackers to hang processing via crafted input. In 9.0.0, 9.1.0, and 9.2.0, parsing fails to terminate; IBM does not disclose the parser, input format, or endpoint. Exploitation requires network reachability but no authentication or user interaction, and the documented consequence is service interruption rather than data access or modification.
Summary
What happened
Parsing-loop DoS in IBM Maximo Application Suite IoT Component allows remote attackers to hang processing via crafted input. In 9.0.0, 9.1.0, and 9.2.0, parsing fails to terminate; IBM does not disclose the parser, input format, or endpoint. Exploitation requires network reachability but no authentication or user interaction, and the documented consequence is service interruption rather than data access or modification.
The record
- CVE
- CVE-2026-75881
- Published
- Oct 12, 2026
- Updated
- Oct 12, 2026
- Vendor
- IBM
- Product
- IBM Maximo Application Suite IoT Component
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 12, 2026CVE publishedPublication date reported by the CVE source.
- Oct 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=9.0.0
- Affected versionversion=9.1.0
- Affected versionversion=9.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started