False positive on cybersecurity requests
Open 💬 3 comments Opened Jul 17, 2026 by koenatdatix
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
codex-cli 0.144.5
What subscription do you have?
ChatGPT Pro 20x
Which model were you using?
gpt-5.6-sol
What platform is your computer?
Linux 6.12.90+deb13.1-amd64 x86_64 unknown
What terminal emulator and version are you using (if applicable)?
Windows Terminal Version: 1.24.11911.0
Codex doctor report
What issue are you seeing?
ⓘ This content can't be shown
We take extra caution with cybersecurity requests. If you’re a security professional, you may be able to apply for Trusted Access.
Trusted Access: https://openai.com/form/enterprise-trusted-access-for-cyber/
Learn more: https://help.openai.com/en/articles/20001326
What steps can reproduce the bug?
Uploaded thread: 019e319e-0b57-70d0-bdcc-a924daaff794
What is the expected behavior?
_No response_
Additional information
_No response_
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I can confirm the same false-positive safety-check behavior in Codex Desktop for Windows.
Feedback session:
019f742b-789f-75a0-ad61-84cb45fc0d38This occurred during explicitly authorized maintenance of my own software in a documented, isolated, disposable local lab. The task was fail-closed and explicitly prohibited access to live, public, or third-party systems; new access or credentials; expansion of targets or network boundaries; downloads; and disclosure of sensitive values.
Despite those constraints, legitimate defensive integration work was repeatedly blocked or hidden with the cybersecurity safety-check message. No unauthorized or harmful activity was requested.
This content can't be showncybersecurity false positiveModel and diagnostic metadata should be associated with the feedback session. Sensitive local paths, hosts, addresses, credentials, and infrastructure details have deliberately been omitted.
+1 Same problem