Quick answers
- Is CVE-2026-3627 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-3627 being exploited in the wild.
- How severe is CVE-2026-3627?
- Critical severity, with a CVSS score of 9.1, published 28 August 2026.
- Which products and versions are affected?
- IBM Concert 1.0.0 through 2.3.1.
- Is there a fix for CVE-2026-3627?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-3627 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-3627?
- Check whether you run IBM Concert or Linux Kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
IBM Concert versions 1.0.0 through 2.3.1 are vulnerable to SQL injection in database query handling. The vulnerability stems from insufficient input validation or parameterization of SQL queries, allowing attackers to inject arbitrary SQL statements. The attack is network-accessible with no authentication required. A successful exploit grants an attacker read, write, and delete access to the entire backend database, potentially exposing or corrupting critical business data. IBM has addressed this issue in version 3.0.0 or later.
Affected products
- IBM Concert 1.0.0 through 2.3.1
Timeline
- 2026-08-28: disclosed