# CVE-2026-14501: Use of Potentially Dangerous Functionthat in IBM Db2 Genius Hub

> Attackers can execute arbitrary code or read sensitive data in IBM Db2 Genius Hub due to unrestricted dangerous function usage.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-2wgw-pqw5-5j5p

## What is CVE-2026-14501?

CVE-2026-14501 is a medium-severity code injection vulnerability in IBM Agentics, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-676 (Use of Potentially Dangerous Function)

## Which versions are affected by CVE-2026-14501?

It affects 2 products.


Products: Ibm Agentics, Ibm Db2 Genius Hub.

## How do I fix CVE-2026-14501?

No fix has been published for CVE-2026-14501 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14501 being exploited?

There is no known exploitation of CVE-2026-14501 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14501 and fix it if it is affected.

What it is: CVE-2026-14501 is a medium-severity code injection vulnerability in IBM Agentics, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14501 in the wild and no public exploit code.

Affected product: IBM Agentics. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14501/ (Markdown: https://insights.sbomify.com/CVE-2026-14501/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14501
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14501
- OSV: https://osv.dev/vulnerability/CVE-2026-14501

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14501/
Summaries are generated and may contain mistakes; the official description above is the record.