How severe is CVE-2026-14501?

CVE-2026-14501 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.

Is CVE-2026-14501 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-14501?

CVE-2026-14501 primarily affects Ibm Agentics. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2026-14501?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2026-14501 published?

CVE-2026-14501 was published on 2026-07-17 and last updated on 2026-08-11.

CVE-2026-14501

CVE-2026-14501 is a medium-severity vulnerability in Ibm Agentics with a CVSS 3.x base score of 4.3. 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-676.

Key facts

Severity: Medium (CVSS 3.x base score 4.3)
EPSS exploit prediction: 0% (24th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-676
Affected product: Ibm Agentics
Published: 2026-07-17
Last modified: 2026-08-11

Description

IBM Db2 Genius Hub 1.1, 1.1.1, 1.1.2 and IBM Agentics 1.0 could allow an attacker to execute arbitrary code or obtain sensitive information due to the use of dangerous functions without sufficient restrictions.

Frequently asked questions

What is CVE-2026-14501?: IBM Db2 Genius Hub 1.1, 1.1.1, 1.1.2 and IBM Agentics 1.0 could allow an attacker to execute arbitrary code or obtain sensitive information due to the use of dangerous functions without sufficient restrictions.
How severe is CVE-2026-14501?: CVE-2026-14501 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2026-14501 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-14501?: CVE-2026-14501 primarily affects Ibm Agentics. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2026-14501?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2026-14501 published?: CVE-2026-14501 was published on 2026-07-17 and last updated on 2026-08-11.

References

https://www.ibm.com/support/pages/node/7279901

Affected products (2)

cpe:2.3:a:ibm:agentics:1.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:db2_genius_hub:*:*:*:*:*:*:*:*

Other CWE-676 vulnerabilities

CVE-2021-27474 — Critical (CVSS 10.0): Rockwell Automation FactoryTalk AssetCentre v10.00 and earlier does not properly restrict all functions relating to IIS…
CVE-2025-14601 — High (CVSS 8.6): An OS command injection vulnerability in vsDesk allows an authenticated attacker with administrative privileges to…
CVE-2022-39063 — High (CVSS 7.5): When Open5GS UPF receives a PFCP Session Establishment Request, it stores related values for building the PFCP Session…
CVE-2025-65117 — High (CVSS 7.4): The vulnerability, if exploited, could allow an authenticated miscreant (Process Optimization Designer User) to embed…
CVE-2024-38434 — Medium (CVSS 6.5): Unitronics Vision PLC – CWE-676: Use of Potentially Dangerous Function may allow security feature bypass
CVE-2024-50307 — Medium (CVSS 5.5): Use of potentially dangerous function issue exists in Chatwork Desktop Application (Windows) versions prior to 2.9.2.…

Browse all CWE-676 vulnerabilities →