Authenticated log falsification via unneutralized special elements
Published Sep 23, 2026 · Updated Sep 23, 2026
Log injection in IBM Concert 1.0.0 through 3.0.0 allows remote authenticated users to falsify log messages through crafted input. IBM has not identified the input field or logging call; affected code writes attacker-controlled special elements to log files without neutralizing them. Low-privileged network access is required, and forged entries can compromise log integrity without exposing data or interrupting service.
Summary
What happened
Log injection in IBM Concert 1.0.0 through 3.0.0 allows remote authenticated users to falsify log messages through crafted input. IBM has not identified the input field or logging call; affected code writes attacker-controlled special elements to log files without neutralizing them. Low-privileged network access is required, and forged entries can compromise log integrity without exposing data or interrupting service.
The record
- CVE
- CVE-2026-6327
- Published
- Sep 23, 2026
- Updated
- Sep 23, 2026
- Vendor
- IBM
- Product
- Concert
- Classifications
- CWE-117
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 23, 2026CVE publishedPublication date reported by the CVE source.
- Sep 23, 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=1.0.0 <=3.0.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