[BUG] CVP approved org still blocked by cyber safeguards — org ID confirmed matching, appeal form shows no fields #84689

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

I'm a Claude Pro subscriber with an approved Cyber Verification
Program (CVP) application. My cyber safeguard requests are still
being blocked despite approval.

Details:

• Organization ID: 1607c800-61e9-4fd1-a4dc-3b978daa02c9
• Organization type: claude_pro (consumer, billed via google_play_subscription)
• I confirmed the org ID matches across: the CVP approval email,
  live session cache in ~/.claude.json (clientDataCacheSlots),
  and the oauthAccount.organizationUuid field
• Models affected: claude-opus-4-8 (auto-fell back to claude-opus-5)
• Request ID: req_011CdnXvFibg45xC2gNwtdyF
• Session ID: fdde06ec-7e3e-49d3-9e83-b5ad2f0dfa4c
• Task context: legitimate threat-hunting / Laravel log analysis
  on my own project

The false-positive appeal form linked from the CVP approval email
(claude.com/form/cyber-block-false-positive-report-cvp-rejection-appeal)
also loads with no visible form fields, so I can't submit an appeal
through the official channel either.

Related issues showing the same

What Should Happen?

CVP-approved organizations should not be blocked by cyber safeguards
for dual-use cybersecurity activities within their approved use case
(defensive threat-hunting / log analysis on my own project).

Error Messages/Logs

API Error: Opus 4.8's safeguards flagged this message. Our 
intentionally broad safeguards allow us to deliver more capabilities 
faster, but can sometimes flag legitimate cybersecurity work. Apply 
to the Cyber Verification Program to reduce these interruptions. 
Send feedback with /feedback or learn more: 
https://support.claude.com/en/articles/14604842-real-time-cyber-safeguards-on-claude

Request ID: req_011CdnXvFibg45xC2gNwtdyF
Request ID: req_011CdnZ1Vf1NpiHf3xbkp4E6

Steps to Reproduce

1. Log in to Claude Code using a Claude Pro account approved for CVP
   (org ID: 1607c800-61e9-4fd1-a4dc-3b978daa02c9)
2. Start a session for legitimate defensive security work
   (e.g. threat-hunting, searching Laravel logs for specific keys)
3. Send a cybersecurity-related prompt
4. Observe that the request is blocked by cyber safeguards, citing
   the same CVP messaging as if never approved
5. Verify org ID match via cat ~/.claude.json —
   oauthAccount.organizationUuid matches the approval email exactly

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.220

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Organization ID: 1607c800-61e9-4fd1-a4dc-3b978daa02c9
Organization type: claude_pro
Billing type: google_play_subscription
Session ID: fdde06ec-7e3e-49d3-9e83-b5ad2f0dfa4c

Model detail: claude-opus-4-8, auto-switched to claude-opus-5
after the block (both blocked in the same session)

Confirmed via ~/.claude.json:

• oauthAccount.organizationUuid: 1607c800-61e9-4fd1-a4dc-3b978daa02c9
  (matches CVP approval email exactly)
• clientDataCacheSlots shows the same org ID recorded live for
  both blocked models at the time of the error

Additional context: I also attempted to submit a report through
the official false-positive appeal form linked in the CVP approval
email (claude.com/form/cyber-block-false-positive-report-cvp-rejection-appeal),
but the page loads with no visible form fields — only a title/header.
This appears to be a known issue also reported by other users in
related threads.

Related issues showing similar patterns (CVP approved but still
blocked, and/or non-functional appeal path):
#69938, #65596, #63751, #69220, #61889, #71442

Screenshots available (block error message + CVP approval email
confirming matching org ID) but failed to upload in this submission
— happy to provide via email or a follow-up comment if needed.