{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-114951 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"No fix has been published for CVE-2026-114951 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-114951 is a high-severity other vulnerability in Oracle Corporation MySQL Cluster, published on 17 Nov 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-114951 and fix it if it is affected.\n\nWhat it is: CVE-2026-114951 is a high-severity other vulnerability in Oracle Corporation MySQL Cluster, published on 17 Nov 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-114951 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\n\nAffected product: Oracle Corporation MySQL Cluster. 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-114951/ (Markdown: https://insights.sbomify.com/CVE-2026-114951/index.md)","id":"CVE-2026-114951","markdown":"https://insights.sbomify.com/CVE-2026-114951/index.md","name":"CVE-2026-114951","record":{"aliases":["GHSA-p9gr-jfv7-5x5v","UBUNTU-CVE-2026-114951"],"analysis":{"component_type":"database","exploitable_when_present":false,"fix_type":"patch","impacts":["code_execution","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"relational database","requires_auth":"high_privilege","requires_specific_call":false,"summary":"A high-privileged network attacker can exploit the MySQL Server logging component to take over the database; MySQL administrators should patch.","user_interaction":"not_required","vuln_class":"other","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"oracle","component":null,"cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Server: Logging).  Supported versions that are affected are MySQL Server: 8.4.0-8.4.13, 9.7.0-9.7.4, 26.10; MySQL Cluster: 8.0.0-8.0.50, 8.4.0-8.4.13, 9.7.0-9.7.4 and  26.10. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server, MySQL Cluster.  Successful attacks of this vulnerability can result in takeover of MySQL Server, MySQL Cluster. CVSS 3.1 Base Score 7.2 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Other in MySQL Cluster","id":"CVE-2026-114951","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"main_cpe":null,"main_fixed":[],"main_package":null,"n_packages":0,"n_references":1,"n_vendor_status":0,"next":{"headline":"Auth bypass in MySQL Cluster","id":"CVE-2026-114952"},"nickname":null,"packages":[],"prev":{"headline":"Other in MySQL Cluster","id":"CVE-2026-114950"},"products":["MySQL Cluster","MySQL Server"],"published":"2026-11-17","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","text_fixes":[],"updated":"2026-11-18","vendor_status":[],"vendors":["Oracle Corporation"]},"summary":"A high-privileged network attacker can exploit the MySQL Server logging component to take over the database; MySQL administrators should patch.","url":"https://insights.sbomify.com/CVE-2026-114951/"}