https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 13:12:33 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2026-19590 <p>OpenAI Codex Desktop for Windows and macOS could execute attacker-controlled Git hooks because automated Git operations trusted the repository&#39;s local core.hooksPath setting. If a user opens an attacker-prepared repository whose preserved .git/config points core.hooksPath to an attacker-controlled directory, Codex can run a malicious hook while processing the repository. The hook executes outside Codex&#39;s command sandbox, without user approval, and with the user&#39;s privileges, allowing it to read, change, or delete the user&#39;s files and access other resources available to the user&#39;s account. An ordinary Git clone does not preserve the attacker-controlled repository-local configuration required for exploitation.</p> <p>OpenAI Codex Desktop for Windows and macOS could execute attacker-controlled Git hooks because automated Git operations trusted the repository&#39;s local core.hooksPath setting. If a user opens an attacker-prepared repository whose preserved .git/config points core.hooksPath to an attacker-controlled directory, Codex can run a malicious hook while processing the repository. The hook executes outside Codex&#39;s command sandbox, without user approval, and with the user&#39;s privileges, allowing it to read, change, or delete the user&#39;s files and access other resources available to the user&#39;s account. An ordinary Git clone does not preserve the attacker-controlled repository-local configuration required for exploitation.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-19590 https://vulnerability.circl.lu/vuln/ghsa-433v-pqvh-w4gj <p>OpenAI Codex Desktop for Windows and macOS could execute attacker-controlled Git hooks because automated Git operations trusted the repository&#39;s local core.hooksPath setting. If a user opens an attacker-prepared repository whose preserved .git/config points core.hooksPath to an attacker-controlled directory, Codex can run a malicious hook while processing the repository. The hook executes outside Codex&#39;s command sandbox, without user approval, and with the user&#39;s privileges, allowing it to read, change, or delete the user&#39;s files and access other resources available to the user&#39;s account. An ordinary Git clone does not preserve the attacker-controlled repository-local configuration required for exploitation.</p> <p>OpenAI Codex Desktop for Windows and macOS could execute attacker-controlled Git hooks because automated Git operations trusted the repository&#39;s local core.hooksPath setting. If a user opens an attacker-prepared repository whose preserved .git/config points core.hooksPath to an attacker-controlled directory, Codex can run a malicious hook while processing the repository. The hook executes outside Codex&#39;s command sandbox, without user approval, and with the user&#39;s privileges, allowing it to read, change, or delete the user&#39;s files and access other resources available to the user&#39;s account. An ordinary Git clone does not preserve the attacker-controlled repository-local configuration required for exploitation.</p> https://vulnerability.circl.lu/vuln/ghsa-433v-pqvh-w4gj