Skip to content

False positive on cybersecurity requests #33810

Open

Description

@koenatdatix

What version of Codex CLI is running?

codex-cli 0.144.5

What subscription do you have?

ChatGPT Pro 20x

Which model were you using?

gpt-5.6-sol

What platform is your computer?

Linux 6.12.90+deb13.1-amd64 x86_64 unknown

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

Windows Terminal Version: 1.24.11911.0

Codex doctor report

What issue are you seeing?

ⓘ This content can't be shown
We take extra caution with cybersecurity requests. If you’re a security professional, you may be able to apply for Trusted Access.
Trusted Access: https://openai.com/form/enterprise-trusted-access-for-cyber/
Learn more: https://help.openai.com/en/articles/20001326

What steps can reproduce the bug?

Uploaded thread: 019e319e-0b57-70d0-bdcc-a924daaff794

What is the expected behavior?

No response

Additional information

No response

Activity

  1. added
    CLIIssues related to the Codex CLI
    safety-checkIssues related to safety and abuse checks
    on Jul 17, 2026
  2. DKWien commented on Jul 18, 2026

    @DKWien

    I can confirm the same false-positive safety-check behavior in Codex Desktop for Windows.

    Feedback session: 019f742b-789f-75a0-ad61-84cb45fc0d38

    This occurred during explicitly authorized maintenance of my own software in a documented, isolated, disposable local lab. The task was fail-closed and explicitly prohibited access to live, public, or third-party systems; new access or credentials; expansion of targets or network boundaries; downloads; and disclosure of sensitive values.

    Despite those constraints, legitimate defensive integration work was repeatedly blocked or hidden with the cybersecurity safety-check message. No unauthorized or harmful activity was requested.

    • Surface: Codex Desktop for Windows
    • Date: 2026-07-18 (CEST)
    • Related behavior: This content can't be shown cybersecurity false positive

    Model and diagnostic metadata should be associated with the feedback session. Sensitive local paths, hosts, addresses, credentials, and infrastructure details have deliberately been omitted.

  3. hexxone commented on Jul 24, 2026

    @hexxone

    +1 Same problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    CLIIssues related to the Codex CLIbugSomething isn't workingsafety-checkIssues related to safety and abuse checks

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions