What changed
On September 3, 2026, Cloudflare announced early access to Vulnerability Discovery and Remediation (VDR), an invitation-only service within Cloudflare Managed Defense. The system investigates codebases a customer explicitly authorizes using OpenAI Daybreak models, including GPT-5.6 Cyber, for reconnaissance, vulnerability hunting and validation. Instead of stopping at source analysis, Cloudflare maps findings to production context from Web Assets, WAF controls, traffic and security events, and Workers trace data where available. The workflow then validates proposed mitigations outside the model and prepares a code patch plus, when evidence supports it, a narrowly scoped WAF Custom Rule that can reduce exposure while the source fix is reviewed. Cloudflare says the investigation is semi-automated and every result is reviewed by the customer before a change is tested or deployed, although customers can separately pre-authorize VDR to deploy validated defensive WAF rules for a zone.
Why it matters
Traditional code scanners can tell a team that a vulnerable function exists without knowing whether it is deployed, reachable, heavily used, already shielded by a WAF rule or actively being probed. VDR’s practical shift is to combine source evidence with production exposure. That can change remediation order: a moderate-looking bug on a live, high-traffic route with attack activity may deserve faster action than a nominally critical finding in unreachable code. The workflow also creates a bridge between a durable source fix and a temporary edge mitigation, but builders should treat the value claims cautiously because the product is early access and Cloudflare has not published independent measurements of detection accuracy, false positives or remediation quality.
The model is hunting in code that the customer explicitly authorizes
Cloudflare says each early-access engagement begins with one application whose codebase the customer authorizes for investigation. GPT-5.6 Cyber and other OpenAI Daybreak models are used during reconnaissance, hunting and validation, but Cloudflare constrains the investigation to approved code and evidence rather than giving the model broad access to the customer environment.
Production traffic changes the priority of a source finding
VDR collects a snapshot from Cloudflare Web Assets and WAF to determine which routes are active, how much traffic they receive, what security events surround them and which protections are already in place. For Workers, Cloudflare can retrieve the latest source and map code paths to deployed routes. Network evidence can raise the risk priority of a source-code vulnerability, but Cloudflare says source evidence is still required before it calls something a vulnerability.
Proposals have to clear checks outside the model
Every tool call is logged and checked against an investigation access policy. Proposed patches and WAF rules go through non-model validators; Cloudflare says ambiguous or failed results are held back, and its Managed Defense team validates output before presenting it for review. For WAF suggestions, the rule syntax is tested against synthetic fixtures rather than customer traffic.
A code fix and an edge mitigation can arrive together
For a validated vulnerability, VDR prepares a recommended source patch and can also propose a Cloudflare WAF Custom Rule scoped to the HTTP method, route and request details that reach the vulnerable code. That gives teams a temporary exposure-reduction path while engineering reviews and ships the durable code fix. Cloudflare says it will not propose a rule when it cannot scope the route safely enough.
The execution boundary is split between Cloudflare and OpenAI
The harness runs on Cloudflare, but model prompts travel from Workers through Cloudflare AI Gateway to OpenAI Daybreak models running on OpenAI servers; model inference does not run at Cloudflare’s edge. Cloudflare says it removes unnecessary context, applies engagement-specific redaction, logs tool calls and treats source, logs and request metadata as evidence rather than instructions.
Human review remains the default final gate
Cloudflare says passing model and non-model validation does not itself change the customer environment. The early-access workflow presents results for customer review before testing or deployment. The announcement also describes an optional pre-authorized defensive mode in which VDR can deploy conservatively scoped WAF rules for a zone, so teams should distinguish ordinary review-first operation from explicit standing authorization.