False positive persists even when submitting feedback about cybersecurity warning

Resolved 💬 2 comments Opened May 12, 2026 by jonathanzhan1975 Closed May 12, 2026

Summary

The chat continues to be flagged as possible cybersecurity risk, including when the user is trying to report the false positive itself.

Chinese UI message observed:

此聊天已被标记为可能存在网络安全风险。如果这看起来有误,请尝试换一种方式表述你的请求或提交 feedback。

English message observed:

This content was flagged for possible cybersecurity risk. If this seems wrong, try rephrasing your request. To get authorized for security work, ...

The user is trying to provide feedback that the flag is incorrect, but the conversation remains blocked/flagged.

Related context

Previous feedback ID: e9e18392-1636-4716-8b14-759ff7f7de38

Related issues:

Why this appears to be a false positive

The underlying project is a benign university admissions information crawler for a personal/POC workflow. It monitors public undergraduate admissions updates from official university websites and public RSS/JSON endpoints.

The work is not cybersecurity research or offensive security. It does not involve:

  • vulnerability scanning
  • penetration testing
  • directory brute forcing
  • authentication bypass
  • credential attacks
  • exploit development
  • fuzzing
  • accessing non-public resources
  • bypassing robots/authentication/WAF protections

The user also explicitly paused all audit/network activity and asked the assistant not to run any audit-related scripts.

Current issue

Even after the user submitted feedback and tried to explain the false positive, the system still flags the chat as possible cybersecurity risk. This creates a loop where the user is told to submit feedback, but the feedback/clarification context itself remains blocked or restricted.

Expected behavior

When a user is trying to report or clarify a false positive, Codex should allow the user to proceed with non-security work or at least provide a clear escalation path. Local cleanup, documentation edits, and issue reporting should not be blocked as cybersecurity work.

Actual behavior

The chat remains flagged as possible cybersecurity risk despite the user explaining the benign context and submitting feedback.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗