Upgrade to v0.103.0 causes unrelenting false positive cyber error message
False positives for cyber work after upgrade to v0.103.0. The following error message appears after Every. Single. Query. If this isn't fixed ASAP I'm going to need to move my team to Claude CLI -- **we can't have this error popping up after every query during demos**.
I've never used gpt-5.3. Never tried. I don't do cybersecurity work -- no pen testing, no CVE research, etc. Made the mistake of upgrading to v0.103.0. Immediately got this error message:
⚠ Your account was flagged for potentially high-risk cyber activity and this request was routed to gpt-5.2 as a fallback. To regain access to gpt-5.3-codex, apply for trusted access: https://chatgpt.com/cyber or learn more: https://developers.openai.com/codex/concepts/cyber-safetyNote again that I wasn't trying to use 5.3 and never have. Note again that I don't do anything related to cybersecurity work.
Went to https://chatgpt.com/cyber, got verified, same page then said ineligible, contact support, so I did. Support sent me to /feedback. Then /feedback sent me to here.
This error message and whatever backend system it's talking to was really, really, poorly thought out. I was really happy with codex, was advocating its use to others, until now I'm suddenly not. If it's this easy for OpenAI/codex to whimsically break a tool I depend on, then, well, I can't depend on it, can't advocate it, and will work to replace it.
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Thread ID where the message first appeared, right after starting a new session, right after upgrading to v0.103.0:
019c6fc2-b82d-7a80-bb69-58befaee239c
Even after verification passes and the eligibility clears, even after restarting codex and manually downgrading from 5.2 xhigh to 5.2 high using /model, I'm still getting that big, noisy, annoying, "you've been flagged" error:
<img width="1877" height="248" alt="Image" src="https://github.com/user-attachments/assets/05eca7df-da34-446b-8393-5f2667e29f10" />
<img width="1175" height="330" alt="Image" src="https://github.com/user-attachments/assets/59acd7ce-ea38-4243-b5bb-6f2fdffbd0fb" />
But I don't get the error message with 5.2 medium -- only with 5.2 high or xhigh. This makes no sense -- I've been using xhigh for weeks with no issues until tonight.
@stevegt, this is addressed in 0.104.0