False positive: routed to GPT-5.2 due to “cyber-abuse risk” during normal dev work
Resolved 💬 4 comments Opened Feb 18, 2026 by HappyMaker7 Closed Feb 20, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the Codex App are you using (From “About Codex” dialog)?
26.217.1959 (669)
What subscription do you have?
Pro
What platform is your computer?
Darwin 25.3.0 arm64 arm
What issue are you seeing?
Hi,
I think my account was incorrectly flagged for “cyber-abuse risk.” Since then, my requests are being re-routed to GPT-5.2 and I’m blocked/downgraded when trying to use GPT-5.3 Codex.
I’m a ChatGPT Pro subscriber and I use Codex only for legitimate development on my own projects (normal “vibe coding”).
What I was doing: standard dev work + connecting to my own server via SSH / using Railway CLI (setup done with Codex).
What I was NOT doing: scanning, exploitation, malware, brute force, or any unauthorized access.
Feedback ID: 019c4491-52ee-7902-9ae4-5685284cc053
Please review and remove the cyber high-risk flag / restore normal access to GPT-5.3 Codex.
What steps can reproduce the bug?
- Open Codex app
- Select GPT-5.3 Codex
- Submit a normal development prompt (not security-related)
- Observe the banner and routing to GPT-5.2
What is the expected behavior?
_No response_
Additional information
_No response_
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Thanks for the duplicate check — this seems to be a widespread issue affecting multiple users (false positive cyber-risk routing / Pro users being re-routed to GPT-5.2).
I also tried verification at https://chatgpt.com/cyber: it briefly showed success (green checkmark), then immediately switched to “Unable to verify your identity.” I’m seeing reports from others that this is a separate verification bug as well.
Could you please review my account as a false positive and remove the cyber-risk restriction / restore normal access (no forced GPT-5.2 routing)?
Feedback ID: 019c4491-52ee-7902-9ae4-5685284cc053
Same issue here.. 3 different docs, 3 differet clients..
Broken deployment/broken code..
Back to Claude it seems, as this is unusable with our workflow
Thanks for the bug report. We're continuing to tune our cyber safety classifiers to make them more accurate. You can read more about this here. If you see this again in the future and believe it's a false positive (i.e. you aren't doing anything related to cybersecurity), please use the
/feedbackslash command and choose "Safety Check" to report it. That will help us further tune our checks.