"This chat was flagged for possible cybersecurity risk" even after KYC verification

Resolved 💬 3 comments Opened Apr 24, 2026 by Dz3131 Closed Apr 24, 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?

v0.124.0

What subscription do you have?

GPT Pro

Which model were you using?

gpt-5.5 xhigh CLI

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

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

Windows Terminal

What issue are you seeing?

I got the message : "This chat was flagged for possible cybersecurity risk" and " Your account was flagged for potentially high-risk cyber activity. Requests may be slower while additional verification is applied. To regain faster acce
ss, apply for trusted access: https://chatgpt.com/cyber or learn more: https://developers.openai.com/codex/concepts/cyber-safety .

I did the KYC verification and I don't do any cybersecurity code with the CLI . I'm using Docker.

What steps can reproduce the bug?

Uploaded thread: 019dbbd0-7d9d-7aa1-a6b6-df593e31c1d2

What is the expected behavior?

_No response_

Additional information

Before the GPT 5.5 I din't receive this message of cybercecurity reasons and what I actually doing is exactly the same. After I did the update of Codex CLI and using GPT 5.5, I got the message after few minutes.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 4 months ago

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

  • #19310
  • #19204
  • #19221
  • #19252
  • #19272

Powered by Codex Action

khaled-wsa · 4 months ago

Same thing is happening to me. Setting aside the fact that it's flagging accounts that are already cyber verified, which needs to be looked into on its own, the flagging should at least be scoped to individual threads, not entire accounts. Just end the flagged thread, or throttle that specific thread. It shouldn't degrade performance across other threads that for example are running normal frontend work.

tartakovsky · 4 months ago

Got this too. Getting it on already verified account while developing my landing page. I'm so dangerous.