IBM Concert 1.0.0 through 3.0.0 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system.
CVE-2026-3626
Score 5.3 from GitHub Security Advisory published 2026-09-23. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 23, 2026
Last Modified
September 23, 2026
Advisory Details (1)
Auto-updated Sep 23, 2026Security Bulletin: Multiple Vulnerabilities in IBM Concert Software
https://www.ibm.com/support/pages/node/7288830Vendor Advisories for CVE-2026-3626(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-23 19:18 UTCEG score recompute
- 2026-09-23 19:18 UTCGHSA enrichment
- 2026-09-23 19:05 UTCEG score recompute
- 2026-09-23 19:04 UTCGHSA enrichment
- 2026-09-23 16:17 UTCEG score recompute
- 2026-09-23 15:54 UTCEG score recompute
- 2026-09-23 15:54 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-209
- CVE-2025-68110EG 9.9CRITICAL
- CVE-2025-59872EG 9.8CRITICAL
- CVE-2026-22778EG 9.8EPSS p90CRITICAL
- CVE-2025-46658EG 9.8CRITICAL
- CVE-2024-6980EG 9.8CRITICAL
- CVE-2026-34045EG 9.1CRITICAL
- CVE-2025-47813NVD 4.3EG 9.0 KEVEPSS p99CRITICAL
- CVE-2024-6984EG 8.8HIGH
- CVE-2025-22218EG 8.5HIGH
- CVE-2025-62168NVD 7.5EG 8.4EPSS p99HIGH
Frequently asked(4)
What is CVE-2026-3626?
When was CVE-2026-3626 disclosed?
What is the CVSS score of CVE-2026-3626?
How do I remediate CVE-2026-3626?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-3626
Is Your Infrastructure Affected by CVE-2026-3626?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.