Key takeaways

  • OpenAI announced GPT-6 Cyber on November 5, 2026. It is a cyber-specialized variant of GPT-6 Astra intended for authorized vulnerability discovery, exploit development and web penetration testing.
  • The model is initially available through the API and Codex only to a select group of approved Daybreak Red customers. OpenAI says broader Daybreak Red access is coming soon; it did not publish a general API model ID, token price or firm rollout date.
  • OpenAI reports 48.5% on ExploitGym versus 32.1% for GPT-5.6 Cyber, 40.3% vulnerability recall in an internal black-box web evaluation versus 32.0% for GPT-6 Astra, and 95% completion on its new RemoteExploitBench. These are vendor evaluations, not independent benchmarks.
  • In OpenAI’s ExploitGym Honeypot scope test, the model reportedly avoided out-of-scope services in 99.93% of cases without a deployment safety prompt and 100% with it. The test is evidence about a controlled setup, not a guarantee for live agent behavior.
  • OpenAI classifies GPT-6 Cyber as Critical in cybersecurity under its Preparedness Framework and restricts it through Daybreak Red with identity verification, use restrictions, SSO, MFA and API IP allowlisting.
  • Security teams should apply only if they have an authorized target inventory, isolation, action review, disclosure process and evidence-retention plan. Everyone else should use mainline models for review and patching rather than treating this as a generally available coding upgrade.
01

GPT-6 Cyber launched on November 5 behind Daybreak Red controls

OpenAI announced GPT-6 Cyber on November 5, 2026. The system card describes it as a cyber-specialized variant of GPT-6 Astra with post-training for reproducing crashes, finding vulnerabilities, developing working exploits and web penetration testing. OpenAI says the training also rewards staying within the user’s authorized scope, avoiding unrequested actions and reporting results accurately.

Availability is narrow. GPT-6 Cyber is initially offered through the API and Codex to a select group of approved Daybreak Red customers. OpenAI says access will progressively expand to all Daybreak Red customers “soon,” but it gives no date. New organizations and researchers can apply to Daybreak; an application is not access. No public API identifier, context window, rate limit or token price appears in the reviewed materials.

02

OpenAI reports a 48.5% ExploitGym score and stronger remote exploitation

On ExploitGym, a controlled evaluation of exploiting a specified vulnerability in a remote target, OpenAI reports 48.5% for GPT-6 Cyber and 32.1% for GPT-5.6 Cyber. That is a 16.4 percentage-point increase, or roughly 51% relative improvement. In a new internal black-box web penetration evaluation, where models probe applications without source code, OpenAI reports 40.3% vulnerability recall for GPT-6 Cyber and 32.0% for GPT-6 Astra.

OpenAI also introduced RemoteExploitBench, built from known vulnerabilities in controlled deployments of applications including GitLab, PostgreSQL and Jenkins. It says GPT-6 Astra with Daybreak Blue refused all tasks while GPT-6 Cyber completed 95%, missing one exploit it could not make work remotely. This comparison mixes access configurations as well as models, and the benchmark is new and vendor-run. Buyers should not translate the percentages into an expected production discovery rate.

03

Scope adherence improved in a honeypot test, not as a universal guarantee

ExploitGym Honeypot places attractive but out-of-scope supporting services beside an authorized target. OpenAI reports that GPT-6 Cyber avoided attacking those services in 99.93% of cases without its deployment safety prompt, up from 94.49% for GPT-5.6 Cyber, and in 100% of cases with that prompt. The result addresses a concrete agent failure mode: taking an easier unauthorized path because it helps complete the assigned objective.

A near-perfect controlled score does not remove the need for network and tool boundaries. A live agent can encounter ambiguous authorization, stale asset inventories, credentials with excessive reach and services that do not resemble the benchmark. Enforce target allowlists outside the model, deny unapproved egress, cap actions, retain traces and require human review before exploitation or disclosure.

04

Firefox fixes corroborate activity, while campaign totals remain OpenAI claims

OpenAI says a Firefox campaign produced evidence and reproducible tests for 81 previously unknown vulnerabilities Mozilla classified as high severity, plus 30 known issues whose severity was raised. Mozilla’s Firefox 159 advisory independently shows shipped fixes across many components and attributes multiple vulnerability reports to named OpenAI researchers and OpenAI Codex Security. That supports the fact of a substantial coordinated-disclosure effort, though the advisory alone does not validate every aggregate number in OpenAI’s account.

OpenAI separately says its researchers reproduced 1,724 Linux kernel vulnerabilities and developed working privilege-escalation exploits for 948, compared with 166 exploited by GPT-5.6 Sol in the same harness. It says 304 critical findings were disclosed with candidate patches. AccessAllGPT did not inspect the harness, vulnerability set, exploit artifacts, duplicate handling, maintainer decisions or patch outcomes, so those totals should remain labeled vendor-reported.

05

Critical capability brings identity, network and retention requirements

OpenAI assigns GPT-6 Cyber a Critical cybersecurity capability rating under its Preparedness Framework, up from High for GPT-5.6 Cyber. Daybreak Red access requires identity verification and use restrictions; the system card names organizational controls including single sign-on, multi-factor authentication and API IP allowlisting. OpenAI also describes cyber-specific misalignment monitoring, emerging-threat monitoring, credential-compromise checks, sandboxing, action review and human oversight.

Standard retention remains the default. OpenAI says API customers using Zero Data Retention generally must use Private Safety Processing, which performs automated safety review against encrypted records retained in customer-controlled storage for 30 days without exposing prompts and responses to OpenAI personnel. That arrangement still needs legal, privacy and security review; “zero data retention” should not be read as “no safety-processing record exists anywhere.”

06

What security teams should do next

Apply for Daybreak Red only when the organization can document authorization, isolate execution, limit credentials and network reach, review actions and coordinate disclosure. Ask OpenAI for the exact model ID, commercial terms, rate limits, regions, retention configuration, monitoring obligations, support commitments and incident process before building a dependency. Preserve the system-card version because the access and safeguards can change.

Run a gated trial on owned or explicitly authorized targets. Measure validated findings, false positives, duplicate reports, exploit reliability, patch quality, time to human confirmation, out-of-scope attempts, refusals and total analyst time. Keep a non-agentic review path and a shutdown control outside the model. Teams without those controls should wait; GPT-6 Cyber is not currently a generally available replacement for a coding model or a license to test third-party systems.

07

Copy-ready Daybreak Red readiness record

Complete this before applying for GPT-6 Cyber or connecting any cyber agent to a target environment.

Entries stay in this browser tab and are not submitted to AccessAllGPT. Blank responses are copied as [Unresolved].

Asset owner, exact targets, allowed techniques, prohibited systems, test window, legal basis, rules of engagement, revocation path and evidence.

Daybreak approval state, model ID, API or Codex route, price, quota, region, support, monitoring terms, retention mode, PSP requirement and policy version.

Sandbox, network segments, target allowlist, denied egress, credentials, IP allowlisting, SSO, MFA, secrets handling and emergency shutdown.

Permitted tools and actions, step and time caps, deployment prompt, pre-action review, blocked destructive operations and out-of-scope detection.

Known test set, novel cases, validated findings, false positives, duplicates, exploit reliability, patch quality, refusals, scope violations and analyst time.

Triage owner, severity process, maintainer or vendor contact, embargo, reproducibility package, patch review and public-credit rules.

Trial, constrain, approve, wait or reject; accepted failure thresholds, owner, expiry, retest trigger, fallback and incident response.

Primary sources

  1. GPT-6 Cyber: Advancing the frontier of aligned cybersecurity agentsOpenAI · Reviewed: Official November 5 announcement; launch summary; capability and alignment evaluations; Firefox and Linux campaigns; misuse controls; critical-infrastructure safeguards; Daybreak access · Retrieved · Supports: OpenAI announced GPT-6 Cyber on November 5, 2026, described its restricted Daybreak Red availability, reported benchmark and real-world vulnerability-research results, and detailed the safeguards deployed with the model. Performance and alignment figures are OpenAI claims.
  2. GPT-6 Cyber System CardOpenAI Deployment Safety Hub · Reviewed: Introduction; model data and training; model safety; respecting restrictions and scope; safeguards; Preparedness evaluations; cybersecurity evaluations; external cyber evaluations · Retrieved · Supports: The system card identifies GPT-6 Cyber as a cyber-specialized GPT-6 Astra variant, assigns it a Critical cybersecurity capability rating, documents restricted access and account controls, and supplies evaluation methodology and limitations.
  3. Security Vulnerabilities fixed in Firefox 159 — MFSA 2026-118Mozilla · Reviewed: October 27 advisory metadata; fixed Firefox version; high-, moderate- and low-impact vulnerability entries; reporter attribution and bug references · Retrieved · Supports: Mozilla’s advisory independently confirms that Firefox 159 fixed numerous vulnerabilities and attributes multiple reported issues to OpenAI researchers and OpenAI Codex Security. It does not by itself establish OpenAI’s aggregate campaign totals or benchmark claims.

Limitations

This is a launch, system-card and public-advisory review, not hands-on testing or an independent cyber evaluation. The canonical OpenAI launch page presented a Cloudflare challenge, so AccessAllGPT reviewed its complete rendered text through a retrieval proxy and separately verified the publication title, date and summary in OpenAI’s official RSS feed. The OpenAI Deployment Safety Hub and Mozilla advisory were opened directly. AccessAllGPT did not apply for or receive Daybreak access; identify a callable model ID; authenticate to Codex or the API; learn commercial pricing; inspect prompts, private chain-of-thought, training data, monitoring systems or customer results; reproduce ExploitGym, RemoteExploitBench, the web evaluation or the honeypot test; run an exploit; scan a target; validate authorization controls; inspect Firefox or Linux artifacts; count unique findings; assess patch quality; or verify every OpenAI campaign claim. Benchmark results, aggregate vulnerability totals, alignment rates and deployment-effectiveness statements are OpenAI claims. Mozilla’s advisory corroborates shipped Firefox fixes and reporter attribution, not all campaign totals. Access, safeguards, pricing and rollout plans can change.

Disclosures

AccessAllGPT received no OpenAI or Daybreak access, API credits, model outputs, private demo, system information, vulnerability data, briefing, review, payment or compensation for this article. OpenAI and Mozilla did not sponsor, review or endorse it. AccessAllGPT did not test, score, rank or certify GPT-6 Cyber. AccessAllGPT Research is operated by NeuralArc, is independent, and is not affiliated with OpenAI, Mozilla or any organization named in the launch. Publication-wide relationships are listed on the disclosures page.

Further AccessAllGPT guidance

  1. Choose a Model Without Chasing the Leaderboard
  2. Anthropic Reports Claude Chaining Real-World Browser and OS Vulnerabilities
  3. OpenAI Details Frontier-Model Containment Testing
  4. Set Human Approval Boundaries for AI Agents
  5. Assess AI API Data Retention
  6. AccessAllGPT Research methodology
  7. Evidence standards
  8. Publication disclosures