{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-105465 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-105465 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-105465 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-105465 in the wild and no public exploit code.\n\nAffected product: IBM Db2. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-105465/ (Markdown: https://insights.sbomify.com/CVE-2026-105465/index.md)","id":"CVE-2026-105465","markdown":"https://insights.sbomify.com/CVE-2026-105465/index.md","name":"CVE-2026-105465","record":{"aliases":["GHSA-7g8w-4g2c-v49j"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"IBM Db2 database","requires_auth":"low_privilege","summary":"Attackers can escalate privileges in IBM Db2 when the db2ssh feature is enabled, requiring a patch to mitigate.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"IBM® Db2® is vulnerable to privilege escalation when db2ssh is enabled with the db2 instance","id":"CVE-2026-105465","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"IBM® Db2® is vulnerable to a denial of service when inserting into a table with XML columns under specific conditions","id":"CVE-2026-105466"},"packages":[],"prev":{"headline":"Privilege escalation in Db2","id":"CVE-2026-105464"},"products":["Db2"],"published":"2026-10-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-13","vendors":["IBM"]},"summary":"Attackers can escalate privileges in IBM Db2 when the db2ssh feature is enabled, requiring a patch to mitigate.","url":"https://insights.sbomify.com/CVE-2026-105465/"}