CVE-2026-6928
CVE-2026-6928 is a critical-severity vulnerability in Ibm Concert with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-416.
Key facts
- Severity: Critical (CVSS 3.x base score 9.8)
- EPSS exploit prediction: 0% (37th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-416
- Affected product: Ibm Concert
- Published:
- Last modified:
Description
IBM Concert 1.0.0 through 3.0.0 references or accesses memory after it has been freed. This allows an attacker who can influence program execution or input may exploit this condition to corrupt memory, cause application crashes, or execute arbitrary code.
Frequently asked questions
- What is CVE-2026-6928?
- IBM Concert 1.0.0 through 3.0.0 references or accesses memory after it has been freed. This allows an attacker who can influence program execution or input may exploit this condition to corrupt memory, cause application crashes, or execute arbitrary code.
- How severe is CVE-2026-6928?
- CVE-2026-6928 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2026-6928 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (37th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2026-6928?
- CVE-2026-6928 affects Ibm Concert. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2026-6928?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
- When was CVE-2026-6928 published?
- CVE-2026-6928 was published on 2026-09-23 and last updated on 2026-09-29.
References
Affected products (1)
- cpe:2.3:a:ibm:concert:*:*:*:*:*:*:*:*
More vulnerabilities in Ibm Concert
- CVE-2026-6730 — Critical (CVSS 9.8): IBM Concert 1.0.0 through 3.0.0 is vulnerable to a buffer overflow, caused by improper bounds checking. A local user…
- CVE-2026-6721 — Critical (CVSS 9.8): IBM Concert 1.0.0 through 3.0.0 allows an unauthenticated remote attacker can supply specially crafted input that is…
- CVE-2026-3627 — Critical (CVSS 9.1): IBM Concert 1.0.0 through 2.3.1 is vulnerable to SQL injection. A remote attacker could send specially crafted SQL…
- CVE-2025-33015 — High (CVSS 8.8): IBM Concert 1.0.0 through 2.1.0 is vulnerable to malicious file upload by not validating the content of the file…
- CVE-2026-6935 — High (CVSS 7.8): IBM Concert 1.0.0 through 3.0.0 invokes operating system commands without fully qualifying executable paths or…
- CVE-2026-6794 — High (CVSS 7.8): IBM Concert 1.0.0 through 3.0.0 has a double free vulnerability that exists due to incorrect memory management. A local…
All CVEs affecting Ibm Concert →
Other CWE-416 (Use After Free) vulnerabilities
- CVE-2026-63795 — Critical (CVSS 10.0): In the Linux kernel, the following vulnerability has been resolved: 9p: avoid putting oldfid in p9_client_walk() error…
- CVE-2026-13782 — Critical (CVSS 10.0): Use after free in Browser in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the…
- CVE-2026-4725 — Critical (CVSS 10.0): Sandbox escape due to use-after-free in the Graphics: Canvas2D component. This vulnerability was fixed in Firefox 149…
- CVE-2026-4688 — Critical (CVSS 10.0): Sandbox escape due to use-after-free in the Disability Access APIs component. This vulnerability was fixed in Firefox…
- CVE-2025-24085 — Critical (CVSS 10.0): A use after free issue was addressed with improved memory management. This issue is fixed in iOS 18.3 and iPadOS 18.3,…
- CVE-2024-43102 — Critical (CVSS 10.0): Concurrent removals of certain anonymous shared memory mappings by using the UMTX_SHM_DESTROY sub-request of…