| CVE-2026-3627 |
IBM Concert 1.0.0 through 2.3.1 is vulnerable to SQL injection
|
9.1
Critical
|
Aug 28, 2026 |
| CVE-2025-64649 |
IBM Concert 1.0.0 through 2.3.1 could allow a remote attacker to perform unauthorized actions using man in the middle…
|
5.9
Medium
|
Aug 28, 2026 |
| CVE-2025-13044 |
IBM Concert 1.0.0 through 2.2.0 creates temporary files with predictable names, which allows local users to overwrite…
|
6.2
Medium
|
Apr 7, 2026 |
| CVE-2025-64648 |
IBM Concert 1.0.0 through 2.2.0 transmits data in clear text that could allow an attacker to obtain sensitive…
|
5.9
Medium
|
Mar 25, 2026 |
| CVE-2025-64647 |
IBM Concert 1.0.0 through 2.2.0 uses weaker than expected cryptographic algorithms that could allow an attacker to…
|
5.9
Medium
|
Mar 25, 2026 |
| CVE-2025-64646 |
IBM Concert 1.0.0 through 2.2.0 could allow an attacker to access sensitive information in memory due to the buffer…
|
6.2
Medium
|
Mar 25, 2026 |
| CVE-2025-36440 |
IBM Concert 1.0.0 through 2.2.0 could allow a local user to obtain sensitive information due to missing function level…
|
5.1
Medium
|
Mar 25, 2026 |
| CVE-2025-36438 |
IBM Concert 1.0.0 through 2.2.0 could allow a privileged user to perform unauthorized actions due to improper…
|
5.1
Medium
|
Mar 25, 2026 |
| CVE-2025-12708 |
IBM Concert 1.0.0 through 2.2.0 contains hard-coded credentials that could be obtained by a local user
|
6.2
Medium
|
Mar 25, 2026 |
| CVE-2025-33088 |
IBM Concert 1.0.0 through 2.1.0 could allow a local user with specific knowledge about the system's architecture to…
|
7.4
High
|
Feb 17, 2026 |
| CVE-2025-33101 |
IBM Concert 1.0.0 through 2.1.0 could allow an attacker to obtain sensitive information using man in the middle…
|
5.9
Medium
|
Feb 17, 2026 |
| CVE-2025-33089 |
IBM Concert 1.0.0 through 2.1.0 could allow a remote attacker to obtain sensitive information or perform unauthorized…
|
6.5
Medium
|
Feb 17, 2026 |
| CVE-2025-36243 |
IBM Concert 1.0.0 through 2.1.0 is vulnerable to server-side request forgery (SSRF)
|
5.4
Medium
|
Feb 17, 2026 |
| CVE-2024-43178 |
IBM Concert 1.0.0 through 2.1.0 uses weaker than expected cryptographic algorithms that could allow an attacker to…
|
5.9
Medium
|
Feb 17, 2026 |
| CVE-2025-36018 |
IBM Concert 1.0.0 through 2.1.0 for Z hub component is vulnerable to cross-site request forgery which could allow an…
|
6.5
Medium
|
Feb 17, 2026 |
| CVE-2025-36019 |
IBM Concert 1.0.0 through 2.1.0 for Z hub framework is vulnerable to cross-site scripting
|
6.1
Medium
|
Feb 17, 2026 |
| CVE-2024-51451 |
IBM Concert 1.0.0 through 2.1.0 is vulnerable to HTTP header injection, caused by improper validation of input by the…
|
6.5
Medium
|
Feb 4, 2026 |
| CVE-2024-43181 |
IBM Concert 1.0.0 through 2.1.0 does not invalidate session after logout which could allow an authenticated user to…
|
6.3
Medium
|
Feb 4, 2026 |
| CVE-2025-33081 |
IBM Concert 1.0.0 through 2.1.0 stores potentially sensitive information in log files that could be read by a local user
|
3.3
Low
|
Feb 3, 2026 |
| CVE-2025-36253 |
IBM Concert 1.0.0 through 2.1.0 uses weaker than expected cryptographic algorithms that could allow an attacker to…
|
5.9
Medium
|
Feb 2, 2026 |
| CVE-2025-33015 |
IBM Concert 1.0.0 through 2.1.0 is vulnerable to malicious file upload by not validating the content of the file…
|
8.8
High
|
Jan 20, 2026 |
| CVE-2025-1722 |
IBM Concert 1.0.0 through 2.1.0 could allow a remote attacker to obtain sensitive information from allocated memory…
|
5.9
Medium
|
Jan 20, 2026 |
| CVE-2025-1719 |
IBM Concert 1.0.0 through 2.1.0 could allow a remote attacker to obtain sensitive information from allocated memory…
|
5.9
Medium
|
Jan 20, 2026 |
| CVE-2025-64645 |
IBM Concert 1.0.0 through 2.1.0 could allow a local user to escalate their privileges due to a race condition of a…
|
7.7
High
|
Dec 26, 2025 |
| CVE-2025-12771 |
IBM Concert 1.0.0 through 2.1.0 is vulnerable to a stack-based buffer overflow, caused by improper bounds checking
|
7.8
High
|
Dec 26, 2025 |