Unauthenticated log injection via unneutralized special elements
Published Sep 3, 2026 · Updated Sep 5, 2026
Log injection in IBM Netezza Software 11.3.0.3 through Interim Fix 002 allows remote attackers to insert forged log data. The affected log-writing path records attacker-controlled special elements without neutralizing them, allowing crafted input to alter log entry boundaries. No authentication or user interaction is required; the established consequence is log integrity loss, and IBM has not identified the specific input field or logging function.
Summary
What happened
Log injection in IBM Netezza Software 11.3.0.3 through Interim Fix 002 allows remote attackers to insert forged log data. The affected log-writing path records attacker-controlled special elements without neutralizing them, allowing crafted input to alter log entry boundaries. No authentication or user interaction is required; the established consequence is log integrity loss, and IBM has not identified the specific input field or logging function.
The record
- CVE
- CVE-2026-9736
- Published
- Sep 3, 2026
- Updated
- Sep 5, 2026
- Vendor
- IBM
- Product
- Netezza Performance Server – Software
- Classifications
- CWE-117, CAPEC-93, T1685
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 3, 2026CVE publishedPublication date reported by the CVE source.
- Sep 5, 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=11.3.0.3 <=Interim Fix 002
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo