CVE-2026-105465 IBM® Db2® is vulnerable to privilege escalation when db2ssh is enabled with the db2 instance
High 8.8
Published
Updated
Check this codebase for CVE-2026-105465 and fix it if it is affected.
What it is: CVE-2026-105465 is a high-severity vulnerability in IBM Db2, published on 12 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-105465 in the wild and no public exploit code.
Affected product: IBM Db2. 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-105465/ (Markdown: https://insights.sbomify.com/CVE-2026-105465/index.md)
Attackers can escalate privileges in IBM Db2 when the db2ssh feature is enabled, requiring a patch to mitigate.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-105465?
CVE-2026-105465 is a high-severity vulnerability in IBM Db2, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 is vulnerable to privilege escalation when db2locssh is enabled with the db2 instance.
Weakness: CWE-269
Which versions are affected by CVE-2026-105465?
How do I fix CVE-2026-105465?
No fix has been published for CVE-2026-105465 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-105465 being exploited?
There is no known exploitation of CVE-2026-105465 in the wild and no public exploit code.
Sources
Also known as GHSA-7g8w-4g2c-v49j.