Cyber Resilience

CVE-2026-14501

Ibm Agentics 1.0

Published
17 July 2026
Modified
11 August 2026
Patch / advisory
View advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0032 24th percentile
Risk Priority 36 floored blend · peak EPSS

Summary

CVE-2026-14501 is a medium-severity Use of Potentially Dangerous Function (CWE-676) vulnerability in Ibm Agentics. Its CVSS base score is 4.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 24th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

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.

CWE(s)
CWE-676

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-25046Same vendor: Ibm
CVE-2023-25927Same vendor: Ibm
CVE-2023-30434Same vendor: Ibm
CVE-2023-47727Same vendor: Ibm
CVE-2026-10535Same vendor: Ibm
CVE-2023-47161Same vendor: Ibm
CVE-2023-45171Same vendor: Ibm
CVE-2024-22338Same vendor: Ibm
CVE-2023-45165Same vendor: Ibm
CVE-2025-36097Same vendor: Ibm

Affected Assets

ibm
agentics
1.0
ibm
db2 genius hub
1.1 — 1.1.3

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and code analysis directly locate calls to unsafe functions.

SA-15 Development Process, Standards, and Tools partial match

Documented standards and tools can explicitly disallow dangerous functions during development.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can mandate safe APIs and ban dangerous functions at design time.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require avoiding or safely wrapping dangerous functions during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can surface instances of dangerous functions but does not prevent their introduction.

A.6.3 Information security awareness, education and training partial match
prevents

Developer security awareness training can teach safe alternatives to risky functions.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC processes include code review and static analysis that can detect use of risky functions.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly ban or restrict dangerous functions such as strcpy, gets, or system.

A.8.19 Installation of software on operational systems none match
none

Controlled software installation reduces exposure to unsafe third-party libraries that may contain dangerous calls.

References