Cybersecurity Scans Blocked Despite Verified Account Status

Open
#35,981 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
rust
Domain
cli, security

Research direction

The report identifies Codex CLI 0.145.0 and an uploaded thread, but names no source file, test, or local reproduction. Start by reviewing the uploaded thread and tracing where cybersecurity scan restrictions are handled; done requires a reproducible case and a clearly defined verified-account behavior.

Written by the indexing model from the issue text.

Description

bug CLI safety-check
What version of Codex CLI is running?

codex-cli 0.145.0

What subscription do you have?

ChatGPT Pro 20x

Which model were you using?

gpt5.6 sol

What platform is your computer?

No response

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

No response

Codex doctor report

What issue are you seeing?

I’m often blocked by cybersecurity-related restrictions while running my scans, even though my account has already been verified for cybersecurity work.

What steps can reproduce the bug?

Uploaded thread: 019face6-aa43-7013-9618-0a06efd19cfc

What is the expected behavior?

Never block scans during the run

Additional information

No response

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.