codex - 💡(How to fix) Fix "This chat was flagged for possible cybersecurity risk" even after KYC verification [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19313Fetched 2026-04-24 10:38:42
View on GitHub
Comments
2
Participants
3
Timeline
7
Reactions
1
Author
Timeline (top)
labeled ×3commented ×2closed ×1cross-referenced ×1
RAW_BUFFERClick to expand / collapse

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.

extent analysis

TL;DR

The issue is likely due to the new cybersecurity risk detection in GPT 5.5, and applying for trusted access may resolve the issue.

Guidance

  • The error message suggests that the account has been flagged for potentially high-risk cyber activity, which may be a false positive.
  • The fact that the issue started after updating to GPT 5.5 and using the gpt-5.5 xhigh CLI model implies that the new model's cybersecurity risk detection may be more sensitive.
  • To mitigate the issue, applying for trusted access as suggested in the error message may help to regain faster access.
  • Reviewing the code and usage to ensure it does not trigger any cybersecurity risk detection algorithms may also be helpful.

Notes

The issue may be specific to the GPT 5.5 model and the xhigh configuration, and more information about the code and usage may be needed to determine the root cause.

Recommendation

Apply for trusted access, as it is the suggested solution in the error message and may help to resolve the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING