CVE-2026-109838 IBM Db2 Genius Hub Improper verification of cryptographic signature
Medium 5.1
Published
Updated
Check this codebase for CVE-2026-109838 and fix it if it is affected.
What it is: CVE-2026-109838 is a medium-severity vulnerability in IBM Db2 Genius Hub, published on 16 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109838 in the wild and no public exploit code.
Affected product: IBM Db2 Genius Hub. 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-109838/ (Markdown: https://insights.sbomify.com/CVE-2026-109838/index.md)
A local attacker can obtain sensitive information due to improper verification of cryptographic signatures in IBM Db2 Genius Hub.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-109838?
CVE-2026-109838 is a medium-severity vulnerability in IBM Db2 Genius Hub, published on 16 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
IBM Db2 Genius Hub 1.0 could allow a local attacker to obtain sensitive information due to improper verification of cryptographic signature.
Weakness: CWE-347
Which versions are affected by CVE-2026-109838?
How do I fix CVE-2026-109838?
No fix has been published for CVE-2026-109838 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-109838 being exploited?
There is no known exploitation of CVE-2026-109838 in the wild and no public exploit code.
Sources
Also known as GHSA-r4f7-pj9x-534w.