cjc0013/patch-first-responsible-disclosure-index

Patch First: Disclosure at Defensive Speed

Supersession notice — effective October 30, 2026. This policy supersedes every earlier cybersecurity, vulnerability-disclosure, and proof-of-concept policy issued by this project, including our prior sanitized approach. Earlier materials are retained only as historical records and are not operative guidance. If any earlier statement conflicts with this policy, this policy controls.

We do not subscribe to “responsible disclosure” when it means giving an affected vendor control over whether—or when—users receive a usable fix.

That model makes public safety contingent on finding the right inbox, receiving a response, avoiding legal threats, and waiting for an organization to prioritize the problem. We will not make patch availability depend on that chain, and we will not initiate outreach as a prerequisite to publishing defensive work.

We are not opposed to maintainers, vendors, private coordination, or confidentiality. We are willing to work privately when doing so produces a concrete security benefit. We are opposed to sending emails into an unaccountable process and calling the resulting silence “coordination.”

This is a documented systemic problem

The failure is not limited to our own ignored reports.

The IETF created security.txt because researchers frequently cannot find any reporting channel or published disclosure practice. It also recognized that one security email address is not a complete disclosure process. RFC 9116

CISA found the problem serious enough to order covered federal agencies to establish formal intake and handling procedures. Its recommended targets were three business days for acknowledgment, seven days for initial assessment, and generally no more than 90 days for resolution. An inbox without tracking, ownership, deadlines, and remediation authority is not a vulnerability-management system. CISA BOD 20-01

CERT/CC uses a default 45-day disclosure deadline regardless of whether a vendor has produced a patch. CERT/CC explicitly notes that researchers may conclude that publication is their only remaining way to induce action when private disclosure produces no adequate response. CERT/CC disclosure policy

ENISA found that legal barriers and lack of stakeholder cooperation were the two greatest impediments to coordinated vulnerability disclosure. Among the participating Member States, 84% said legal barriers had at least some impact, while 89% said lack of cooperation impeded CVD policy. ENISA’s CVD study

The United States Department of Justice did not expressly direct prosecutors to exclude good-faith security research from CFAA charges until 2022. That policy was important, but it is not universal civil or international safe harbor. Its existence demonstrates that legal uncertainty is a real disclosure cost. DOJ CFAA policy announcement

Even successful coordinated-disclosure programs depend on externally enforced clocks. Google Project Zero reported that average fix time for its reports fell from approximately 80 days to 52 days over three years under a deadline regime, although it properly cautioned that its sample was limited. Its current policy retains a 90-day fix deadline and up to 30 days for patch adoption. Project Zero has also identified the “upstream patch gap”: a fix may exist while downstream products and actual users remain exposed. Project Zero metrics, 2025 disclosure policy

Deadlines help precisely because goodwill and email alone are insufficient.

PHP demonstrates the structural failure

The recent PHP case is not evidence that PHP’s maintainers are malicious or indifferent. It is evidence that a conventional human coordination process can fail structurally even when competent people are involved.

According to the PHP Foundation, the first signs appeared in 2024, but work stalled and restarted over a period of months. The Foundation itself described this as a structural failure. Critical fixed releases ultimately arrived on October 21, 2026. PHP Foundation account

Wiz reports sending its vulnerabilities to the PHP security team on August 24, receiving acknowledgment on September 21, and seeing patched releases on October 21: 28 days to acknowledgment and 58 days to patched releases. Wiz technical account

The broader timeline then compressed under CVE circulation, an accidentally published proof-of-concept video, possible mitigation leakage, and early publication of fixed images. PHP2Shell timeline

This is exactly the brittleness we reject: the defender’s timetable depends on inboxes, human availability, confidentiality holding across multiple parties, and information not leaking while the patch remains unavailable.

Binance demonstrates the cost of defensive delay

Binance’s preliminary account of its October 2026 incident says a possibly compromised DevOps laptop enabled access to service containers and unauthorized withdrawal transactions. Binance estimated approximately $6.3 billion in impact, of which roughly $3 billion had been frozen at the time of its update. Binance’s preliminary update

This does not prove a vulnerability-disclosure failure. It demonstrates the consequences of control failure and the scale at which defenders must now operate. A defensive model that depends on someone reading an email, scheduling a meeting, and manually moving a fix through several organizations is mismatched to that risk.

Attack operates at machine speed; defense remains at human speed

CrowdStrike reported a 29-minute average eCrime breakout time for 2025 and a fastest observed breakout of 27 seconds. CrowdStrike 2026 Global Threat Report

Unit 42 reported that the fastest quartile of investigated intrusions reached data exfiltration in approximately 72 minutes during 2025, down from approximately 285 minutes the previous year. Unit 42 Global Incident Response Report

Microsoft describes attack timelines as compressing while agentic systems automate increasing portions of the attack chain. Microsoft Digital Defense Report 2026

OpenAI similarly warns that defenders must prepare for AI-enabled attackers operating faster, at greater scale, and with better coordination than human attackers. OpenAI’s incident analysis

Against this background, Sam Altman recently said: “I no longer think we’re going to be able to just patch all the bugs.” He argued that cybersecurity requires a new defensive model using the same technology to construct a defensive shield. Stanford GSB interview

A process measured in 45- or 90-day disclosure windows cannot be the complete answer to adversaries moving in seconds or minutes. Responsible disclosure remains a human-speed workflow in an increasingly machine-speed threat environment.

Our patch-first policy

Our objective is to get usable defensive artifacts into people’s hands.

At time T0, we publish:

• A reviewable patch or mitigation.
• Exact affected versions and applicability information.
• Reproduction and regression tests where safely possible.
• Build, deployment, and rollback instructions.
• A concise advisory containing enough information to evaluate urgency without unnecessarily operationalizing exploitation.
• Cryptographic hashes and provenance for the released artifacts.

We do not require prior vendor outreach. The patch itself becomes the primary defensive communication.

The X-day proof-of-concept reserve

X is the declared PoC reserve period beginning at T0, the verified patch-publication time. Our default is X = 30 calendar days, matching a recognizable patch-adoption interval while avoiding an open-ended embargo.

During those X days:

• The operational proof of concept remains private.
• Maintainers, downstream projects, and independent defenders can validate and adopt the patch.
• We remain open to inbound private collaboration.
• A receipt, acknowledgment, or promise does not stop the clock.

A substantive response means verifiable integration, independent technical validation, demonstrated downstream adoption, or a concrete private remediation plan with an owner and dated milestone.

If no substantive response occurs by T0 + X, we may publish a minimized PoC sufficient to verify the vulnerability and the patch. It should demonstrate the security boundary without adding persistence, scale-out automation, destructive behavior, or unnecessary weaponization.

If concrete private cooperation is producing a measurable benefit, the PoC may remain private beyond X. Any extension must have a specific milestone and new review date. Silence, vague assurances, or indefinite process do not qualify.

Patch-first is necessary—and still does not go far enough

Patch-first fixes one failure: it removes the affected vendor’s ability to become a single point of failure for patch availability.

It does not solve:

• Discovery and reproduction latency.
• Patch generation and regression testing.
• Dependency and affected-version identification.
• Downstream integration.
• Deployment and patch adoption.
• Emergency containment.
• Verification that users actually received the fix.
• Safe rollback when a patch causes regressions.

Those stages remain largely human-paced. The ultimate defensive objective must therefore be a machine-speed loop, not merely faster publication.

Ouroboros as one theoretical component

This is a counterfactual design proposal, not a claim about Ouroboros’s present capabilities.

If Ouroboros were scaled—supplied with adequate compute, telemetry, isolated test environments, repository access, and independent validators—and granted bounded authority to act, it could theoretically operate as part of a machine-speed defensive system:

1. Continuously discover and reproduce suspected vulnerabilities in isolated environments.
2. Identify affected versions and downstream dependencies.
3. Generate candidate patches, regression tests, and temporary mitigations.
4. Challenge its own findings through independent reproduction, negative controls, and competing patch candidates.
5. Publish signed, machine-readable defensive artifacts when predefined evidence gates pass.
6. Deploy high-confidence fixes to opted-in systems through staged canaries.
7. Automatically roll back deployments that violate health or security invariants.
8. Apply reversible, time-limited containment while lower-confidence fixes undergo further validation.
9. Measure patch propagation and maintain an auditable X-day PoC reserve clock.

Its authority would need to be tiered:

Authority	Theoretical action
Observe	Detect, reproduce, analyze, and propose without changing external systems.
Publish	Release signed patches and advisories after deterministic validation gates pass.
Deploy	Canary and progressively deploy fixes only within explicitly delegated environments.
Contain	Apply reversible, time-limited controls such as isolation or credential revocation within that delegated scope.
Escalate	Require separate human or external authority for irreversible, destructive, cross-organizational, or legally ambiguous actions.

This would not be unlimited autonomy. Every action would require provenance, bounded scope, independent verification, an audit receipt, canarying where applicable, and a tested rollback path. Unauthorized exploitation, indiscriminate disclosure, and action against systems outside the delegated defensive scope would remain prohibited.

The point is not that Ouroboros alone solves cybersecurity. The point is that a scaled system with carefully bounded authority could help move defense from an email queue to a continuous detect–verify–repair–deploy–rollback loop.

Humans would define policy, authority, and acceptable risk. They would audit exceptions and govern irreversible decisions. They would no longer be required to manually approve every routine defensive step while an automated adversary moves in seconds.

Conclusion

Responsible disclosure assumes that finding the right recipient and waiting for human coordination is normally the safest path. The historical record shows that reporting channels can be absent, messages can be ignored, legal risk can discourage researchers, remediation can stall, confidentiality can fail, and patches can take too long to reach users.

Our immediate answer is patch first, followed by an X-day PoC reserve.

Our longer-term answer must go further: defensive systems capable of discovering, validating, distributing, deploying, and rolling back protections at the speed at which modern attackers operate.

An unanswered email is not a security strategy.