{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92903 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-92903 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-92903 is a high-severity SQL injection vulnerability in Snowflake CLI, published on 17 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-92903 and fix it if it is affected.\n\nWhat it is: CVE-2026-92903 is a high-severity SQL injection vulnerability in Snowflake CLI, published on 17 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-92903 in the wild and no public exploit code.\n\nAffected product: Snowflake CLI. 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-92903/ (Markdown: https://insights.sbomify.com/CVE-2026-92903/index.md)","id":"CVE-2026-92903","markdown":"https://insights.sbomify.com/CVE-2026-92903/index.md","name":"CVE-2026-92903","record":{"aliases":["GHSA-p2xq-qfx5-xp6q"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Snowflake CLI","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary SQL via malicious configs or inputs in Snowflake CLI, potentially escalating privileges within the victim's session.","user_interaction":"required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SNOWFLAKE","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Improper input validation in Snowflake CLI versions prior to 3.27.0 allowed unsanitized user-controlled values to be interpolated into SQL strings that are executed as multi-statement queries. An attacker who is able to supply a malicious project configuration file or craft command-line input can cause Snowflake CLI to execute attacker-controlled SQL statements in the context of the victim's Snowflake session and active role. Successful exploitation requires either write or pull-request access to a project repository whose CI/CD pipeline runs Snowflake CLI under an elevated service account role, or the ability to supply untrusted input to CLI-wrapping automation. Impact is limited by the privileges held by the configured Snowflake role at execution time. The fix is available in Snowflake CLI version 3.27.0, which also addresses several additional security findings. Users must manually upgrade.","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":"SQL injection in Snowflake CLI","id":"CVE-2026-92903","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Rubygem-foreman_remote_execution: job output readable without object-level view_job_invocations check","id":"CVE-2026-92904"},"packages":[],"prev":{"headline":"Apache WSS4J: UsernameToken replay protection bypassed by re-encoding the Nonce","id":"CVE-2026-92899"},"products":["Snowflake CLI"],"published":"2026-09-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","updated":"2026-09-17","vendors":["Snowflake"]},"summary":"Attackers can execute arbitrary SQL via malicious configs or inputs in Snowflake CLI, potentially escalating privileges within the victim's session.","url":"https://insights.sbomify.com/CVE-2026-92903/"}