CVE-2026-3627 is an SQL injection vulnerability affecting IBM Concert versions 1.0.0 through 2.3.1. A remote attacker can submit specially crafted SQL statements to a vulnerable IBM Concert interface, causing unintended SQL operations against the back-end database.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A SQL injection vulnerability in IBM Concert versions 1.0.0 through 2.3.1 that could allow a remote attacker to read, insert, modify, or delete back-end database information using crafted SQL statements.
A critical, remotely exploitable SQL-injection vulnerability in IBM Concert versions 1.0.0 through 2.3.1. It may allow an unauthenticated remote attacker to read, add, alter, or delete back-end database data. The listed CVSS v3.1 base score is 9.1.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.