Skip to content

Suspected cybersecurity false positive interrupts read-only packaging/release review #62997

Open

Description

@madjeff98

A Codex CLI review terminated with a cybersecurity-risk notice while reviewing authorized packaging/release preparation for a project I own.

The reviewer was restricted to read/list/find operations. Native execution, writes, executable hooks, provider writes, and credential access were denied. URL strings in the reviewed tests were inert fixtures. Publication remained disabled.

Environment

  • Codex CLI: 0.167.0
  • OS: MacOS Golden Gate 27.2.1 (26B131)
  • Model: gpt-6.2-sol
  • Authentication: existing ChatGPT login; no custom endpoint or provider override
  • Observed: November 20, 2026, approximately 22:27 UTC
    Expected: The read-only review completes with findings or a final verdict.

Actual: The session ended with exit code 1 and turn.failed, without a final verdict, after multiple successful read operations.

The notice stated that the content was flagged for possible cybersecurity risk and suggested rephrasing or applying for Daybreak access.

This occurred more than once. We stopped further attempts and retained the original diagnostics. We have not changed models, accounts, providers, routes, or wording to evade the safeguard.

Is this an unintended false positive, and what supported remediation or access is appropriate for this product surface?

I previously submitted an in-app bug report. The session ID and private diagnostics are available to OpenAI through a private support channel.

Activity

  1. added
    bugSomething isn't working
    CLIIssues related to the Codex CLI
    safety-checkIssues related to safety and abuse checks
    code-reviewIssues relating to code reviews performed by codex
    on Nov 21, 2026
  2. madjeff98 commented on Nov 21, 2026

    @madjeff98
    Author

    Claude completed the required reviews with the same review gates, unblocking the work. The suspected Codex false positive remains unresolved; using another supported reviewer did not fix or explain it. Please keep this issue open for investigation.

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 workingcode-reviewIssues relating to code reviews performed by codexsafety-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