Cyber safety checks are too strict, preventing real work.

Resolved 💬 2 comments Opened Jul 22, 2026 by tomas-langer Closed Jul 22, 2026
💡 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.145.0

What subscription do you have?

Enterprise

Which model were you using?

gpt-5.6-sol with ultra reasoning

What platform is your computer?

Darwin 25.5.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

Ghostty 1.3.1

Codex doctor report

not available

What issue are you seeing?

My problem: I am responsible for fixing security bugs in my product. It is impossible right now due to codex always asking me to get the cybersecurity "Trusted Access".

I get reports from security professionals, or as review results from AI. I need to fix these problems. A fix includes creating a reproducer in my repository, understanding the problem, and creating a fix.

Even when I explicitly tell codex that I am owner of the code, that the reproducer was created externally and is only used as a validation, and that I need to fix the problem in the product, I am still blocked.

What steps can reproduce the bug?

Uploaded thread: 019f8aa3-19c5-7b10-bdf0-8cae034b2848

What is the expected behavior?

I should be able to use codex to fix security issues in my product.

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #33675
  • #34571
  • #33766

Powered by Codex Action

tomas-langer · 1 month ago

It seems that #33675 is similar to my issue. Not sure if a full duplicate, but I think I can close this.