{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-66816 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-66816 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-66816 is a medium-severity vulnerability in Microsoft Sql Server 2022, published on 8 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-66816 and fix it if it is affected.\n\nWhat it is: CVE-2026-66816 is a medium-severity vulnerability in Microsoft Sql Server 2022, published on 8 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-66816 in the wild and no public exploit code.\n\nAffected product: Microsoft Sql Server 2022. 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-66816/ (Markdown: https://insights.sbomify.com/CVE-2026-66816/index.md)","id":"CVE-2026-66816","markdown":"https://insights.sbomify.com/CVE-2026-66816/index.md","name":"CVE-2026-66816","record":{"aliases":["GHSA-c9p4-3ww6-v9gp"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Microsoft SQL Server","requires_auth":"low_privilege","summary":"An authorized attacker can bypass security features in Microsoft SQL Server due to insufficient logging mechanisms.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"sql_server_2022","vendor":"microsoft"},{"product":"sql_server_2025","vendor":"microsoft"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C","version":"3.1"},"cwes":[{"id":"CWE-778","name":"Insufficient Logging"}],"description":"Insufficient logging in SQL Server allows an authorized attacker to bypass a security feature over a network.","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":"Microsoft SQL Server Security Feature Bypass Vulnerability","id":"CVE-2026-66816","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:sql_server_2022","products":["microsoft:sql_server_2022","microsoft:sql_server_2025"],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Microsoft SQL Server Elevation of Privilege Vulnerability","id":"CVE-2026-66818"},"packages":[],"prev":{"headline":"Microsoft SQL Server Elevation of Privilege Vulnerability","id":"CVE-2026-66814"},"products":["Microsoft SQL Server 2022 (CU 26)","Microsoft SQL Server 2022 (GDR)","Microsoft SQL Server 2025 (CU8)","Microsoft SQL Server 2025 for x64-based Systems (GDR)"],"published":"2026-09-08","related":[{"cvss_score":9.8,"headline":"Microsoft SQL Server Remote Code Execution Vulnerability","id":"CVE-2026-67643","kev_date_added":null,"published":"2026-09-08"},{"cvss_score":8.8,"headline":"SQL Server Remote Code Execution Vulnerability","id":"CVE-2026-78456","kev_date_added":null,"published":"2026-09-08"},{"cvss_score":8.8,"headline":"Microsoft SQL Server Elevation of Privilege Vulnerability","id":"CVE-2025-47954","kev_date_added":null,"published":"2025-08-12"},{"cvss_score":7.2,"headline":"Microsoft SQL Server Elevation of Privilege Vulnerability","id":"CVE-2026-20803","kev_date_added":null,"published":"2026-01-13"},{"cvss_score":6.5,"headline":"Microsoft SQL Server Information Disclosure Vulnerability","id":"CVE-2026-67389","kev_date_added":null,"published":"2026-09-08"},{"cvss_score":6.5,"headline":"Microsoft SQL Server Denial of Service Vulnerability","id":"CVE-2026-67641","kev_date_added":null,"published":"2026-09-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-10-14","vendors":["Microsoft"]},"summary":"An authorized attacker can bypass security features in Microsoft SQL Server due to insufficient logging mechanisms.","url":"https://insights.sbomify.com/CVE-2026-66816/"}