AI models now find software vulnerabilities faster than maintainers and operators can fix them, and the US government has responded with a clearinghouse called Gold Eagle. Announced by the White House on 14 July 2026 under Executive Order 14409, Gold Eagle takes in vulnerability findings from government and industry, deconflicts scanning, prioritises the most consequential flaws and pushes remediation guidance to defenders. It is a voluntary coordination programme built on existing federal authorities, not a regulation, and much of its operating detail is still unpublished. This guide sets out what is confirmed, what is not, how it fits with CVD, CVE and the CISA KEV catalogue, and how vulnerability management teams, open-source maintainers and critical infrastructure operators should prepare. Status line: checked against whitehouse.gov and reporting up to 2 November 2026.
Source note: the clearinghouse's basis comes from the executive order and White House material, with launch and participation details from named reporting. Status is as of November 2026. Confirm against the official text before relying on it.
Key takeaways
- Gold Eagle comes from Section 2(d) of EO 14409. The order of 2 June 2026 directed the Secretary of the Treasury to form an AI cybersecurity clearinghouse within 30 days, in consultation with the National Cyber Director, the NSA Director and the CISA Director.
- Participation is voluntary and nothing is compelled. The order frames it as voluntary collaboration with the AI industry and critical infrastructure operators, and reporting notes it does not force anyone to patch.
- It is already operating, but opaquely. The White House says it has begun to intake and prioritise vulnerabilities; participant lists, finding counts, triage criteria and data handling rules have not been published.
- Coordination runs through VINCE. Cybersecurity Dive reports that the government is using the Vulnerability Information and Coordination Environment, run with Carnegie Mellon University's Software Engineering Institute, so anyone can report into Gold Eagle.
- The legal shield for sharing is temporary. Liability protections under the Cybersecurity Information Sharing Act of 2015 were extended only to 11 December 2026 as of early November, so check counsel advice before submitting proprietary findings.
Scope: who and what is covered
Gold Eagle covers software vulnerabilities found by any party, with an emphasis on flaws discovered using frontier AI models, in open-source software and in systems that underpin US critical infrastructure. The White House release names the participants as the White House, the Department of the Treasury, the Department of Homeland Security through CISA and the Department of War, together with open-source software partners and American critical infrastructure companies.
| Party | Role as published | Source |
|---|---|---|
| Secretary of the Treasury | Forms the clearinghouse (lead under EO 14409 Sec. 2(d)) | EO 14409 |
| National Cyber Director | Consulted on formation; public spokesperson at launch | EO 14409, White House release |
| Secretary of War through the NSA Director | Consulted on formation | EO 14409 |
| Secretary of Homeland Security through the CISA Director | Consulted on formation; CISA named as participant | EO 14409, White House release |
| Open-source software partners | Receive and fix prioritised findings | White House release |
| Critical infrastructure companies | Contribute and receive findings and remediation guidance | White House release |
| AI developers | Voluntary collaborators; Anthropic said on 30 June 2026 it would participate | EO 14409, Nextgov |
What is not covered matters as much. Gold Eagle does not replace CVE assignment, NIST's National Vulnerability Database, the CISA KEV catalogue or any organisation's own coordinated vulnerability disclosure (CVD) process. It is an additional coordination and prioritisation layer on top of them. It creates no obligations for organisations that choose not to take part, and EO 14409 Section 5 states that the order creates no enforceable rights.
Key obligations
EO 14409 places obligations on the federal government, not on companies. Section 2(d) gives the clearinghouse three functions, which are the closest thing to a published charter:
- Coordinate and deconflict vulnerability scanning: stop multiple AI labs and researchers scanning the same packages and flooding the same maintainers.
- Discover and validate vulnerabilities: verify findings before they are pushed to defenders, which the White House describes as coordinating scanning verifications.
- Coordinate and prioritise remediation and patch distribution: deliver what the release calls prioritised and actionable threat and remediation information to defenders.
The same order contains neighbouring provisions that shape the environment Gold Eagle works in:
| EO 14409 section | Requirement (summarised) | Why it matters for vulnerability teams |
|---|---|---|
| Sec. 2(c) | CISA to issue directives within 30 days, including to facilitate access to cybersecurity tools and services, where appropriate covered frontier models, for state and local authorities and critical infrastructure operators | Smaller operators may gain access to AI scanning, increasing finding volume |
| Sec. 2(d) | Treasury to form the AI cybersecurity clearinghouse within 30 days | Basis of Gold Eagle |
| Sec. 2(e) | OMB to determine within 30 days whether federal grant funds can support advanced AI vulnerability detection | Possible funding route for public bodies |
| Sec. 3 | Classified benchmarking and a voluntary framework for covered frontier models; developers may give government access up to 30 days before release | Explains why AI labs feed findings to government early |
| Sec. 3(c) | States that nothing in the order authorises mandatory governmental licensing of AI models | Confirms the voluntary model |
| Sec. 4 | Attorney General to prioritise prosecuting criminal misuse of AI to access computers illegally | Context for researcher conduct |
For federal civilian agencies, the practical pressure comes from CISA's separate update to remediation timelines, which Nextgov and Paul Hastings report as three days for the highest-risk flaws up to 60 days for lower-priority issues. Treat that as reported: confirm the directive text on cisa.gov before building agency SLAs on it. See the CISA Binding Operational Directives Guide.
Timeline and current status
| Date | Event | Source |
|---|---|---|
| 2 June 2026 | EO 14409 "Promoting Advanced Artificial Intelligence Innovation and Security" signed; Sec. 2(d) sets a 30-day deadline for the clearinghouse | whitehouse.gov |
| 30 June 2026 | Anthropic states it will give federal officials advance access to threat intelligence and take part in the clearinghouse | Nextgov |
| 14 July 2026 | White House launches Gold Eagle and says it has already begun intake and prioritisation | whitehouse.gov |
| 15 July 2026 | CISA, NSA and international partners publish separate guidance on establishing CVD programmes | Covington (Inside Privacy) |
| Late September 2026 | Stopgap funding bill extends Cybersecurity Information Sharing Act 2015 protections | Defense One |
| 11 December 2026 | Current expiry of the 2015 Act's liability protections unless Congress extends them; a House defence authorisation provision (H.R. 8800) would run them to 2035 | Defense One (2 November 2026) |
As of 11 November 2026 there is no public Gold Eagle charter, no published intake form beyond VINCE, no stated severity method and no time-to-patch targets. The Cloud Security Alliance research note lists the open questions: no dispute process for conflicting severity ratings, no confirmation timelines, no published controls on who can see pre-disclosure data, and no criteria for safe deployment of fixes in OT and ICS environments. Expect detail to change, and re-check the White House and CISA pages before relying on any process step.
Related private initiatives: Cybersecurity Dive reports overlap with Akrites, created by the Linux Foundation with support from Anthropic, Microsoft and others, and Athena, launched by Chainguard with partners including Cisco and Cloudflare. A maintainer may receive the same finding from more than one route.
Enforcement and penalties
There are none. Gold Eagle is a voluntary coordination mechanism using what the White House calls the existing authorities and resources of the federal government. It does not compel vendors to fix flaws, and EO 14409 is to be implemented consistent with applicable law and subject to appropriations. The real legal exposure is elsewhere:
- Information sharing liability: sharing threat and vulnerability data with government relies on the protections in the Cybersecurity Information Sharing Act of 2015, currently extended only to 11 December 2026. Paul Hastings advises organisations to assess liability exposure before sharing.
- Contractual and customer restrictions: findings about a customer's or supplier's product may be covered by NDAs, bug bounty terms or embargoes. Check before forwarding.
- Federal agency directives: agencies remain bound by CISA directives, including KEV-driven remediation. See the CISA KEV Catalogue Guide.
- Non-US regimes: a vendor selling into the EU still has to report actively exploited vulnerabilities under the Cyber Resilience Act from 11 September 2026, whatever it shares with Gold Eagle. See the EU Cyber Resilience Act Vulnerability and Incident Reporting Guide.
What it means for AI agents and non-human identities
Gold Eagle exists because autonomous AI scanning has changed the economics of discovery. Three identity questions follow:
- Scanner identities: AI scanning agents that probe repositories and services run under API keys, tokens and cloud workload identities. Treat them as privileged non-human identities: scope them to the targets in the engagement, rotate them, and log every scan so that deconfliction requests from the clearinghouse can be answered. See the AI for Vulnerability Discovery and Triage Guide.
- Pre-disclosure data access: a shared pipeline of unpatched vulnerabilities is a high-value target. VINCE accounts, integration tokens and any automation that pulls findings into ticketing systems need MFA, least privilege and access review, because a stolen token would expose a queue of zero-days.
- Vulnerabilities in identity infrastructure: many of the most consequential flaws sit in identity providers, secrets managers, CI/CD runners and remote access gateways. When prioritised guidance arrives, check whether the fix also requires rotating the credentials the vulnerable component held, not just patching it. Credential theft through software supply chain compromise maps to ATT&CK T1195.002 Compromise Software Supply Chain and exploitation of exposed services to T1190 Exploit Public-Facing Application.
Compliance steps
Because nothing is mandatory, "compliance" here means readiness to send and receive through the clearinghouse without legal or operational surprises.
- Decide whether to participate (first month): legal, security and the product owner agree whether to submit findings, what data may leave the organisation and who signs off. Record the decision and revisit it when the 2015 Act status changes.
- Set up the intake channel: register a role-based account in VINCE (never a personal one), protect it with MFA, and document who can see what. Confirm a CISA point of contact for prioritised alerts.
- Connect to your CVD process: route Gold Eagle findings into the same handling process you use under ISO/IEC 30111, so triage, fix and advisory steps do not fork. See the ISO/IEC 29147 and 30111 Vulnerability Disclosure and Handling Guide.
- Reconcile priority signals: decide in advance how a Gold Eagle priority ranks against KEV listing, EPSS, SSVC and your own asset criticality. Write the rule down so analysts do not argue it case by case. See the Vulnerability Prioritisation Guide.
- Test surge capacity: run a tabletop where 50 validated findings arrive in a week. Measure how many your team and maintainers can fix, and agree what gets deferred.
- Protect OT change processes: treat clearinghouse guidance as an input to OT patch validation, not a bypass. Roll back by keeping the previous version and a tested restore path before deploying any urgent fix.
- Review quarterly: update the runbook as the White House, Treasury or CISA publish operating detail.
Decision guidance
- Open-source maintainers: joining gives earlier, deduplicated reports, but expect volume. Publish a SECURITY.md that names your preferred channel and response expectations. See the Open Source Project Maintainer Security Guide.
- Large vendors with mature PSIRTs: participation mainly reduces duplicate inbound reports; keep your own CVE numbering and advisories authoritative.
- Small critical infrastructure operators: the main benefit is receiving prioritised guidance and, via EO 14409 Sec. 2(c), possible access to AI tools. Without patch capacity, prioritised guidance only grows the backlog, a point the CSA note makes.
- Organisations holding customer findings: do not submit until contracts and embargoes are cleared.
Detection and measurement
- Time to triage: median hours from Gold Eagle or VINCE receipt to a validated internal ticket.
- Time to remediate by priority: days to fix for clearinghouse-prioritised findings versus your baseline.
- Duplicate rate: share of inbound findings already known from another channel, which shows whether deconfliction is working.
- Backlog growth: open validated findings per maintainer or product team month on month.
- Access hygiene: number of accounts and tokens with access to pre-disclosure data, reviewed quarterly.
Framework mapping
| Gold Eagle activity | NIST SP 800-53 Rev 5 | NIST CSF 2.0 |
|---|---|---|
| Receive and act on external vulnerability reports | RA-5(11) Public Disclosure Program; SI-5 Security Alerts, Advisories, and Directives | ID.RA-08 |
| Scan, validate and record vulnerabilities | RA-5 Vulnerability Monitoring and Scanning | ID.RA-01 |
| Prioritised patch remediation | SI-2 Flaw Remediation | ID.RA-01 |
| Participate in sharing communities | PM-15 Security and Privacy Groups and Associations | ID.RA-02 |
| Supplier notification arrangements | SR-8 Notification Agreements | ID.RA-08 |
Common failure patterns
- Optimising discovery, not repair: joining every finding feed while patch capacity stays flat simply grows the queue.
- Personal accounts on coordination platforms: analysts leave and pre-disclosure data stays reachable through their credentials.
- Two priority systems with no tie-breaker: teams stall when Gold Eagle, KEV and internal scoring disagree.
- Sharing before legal review: submitting customer or partner findings breaches NDAs or embargoes.
- Patching without rotating: fixing a vulnerable secrets or CI component but leaving the credentials it exposed in place.
Practitioner checklist
- Read EO 14409 Sec. 2 and the 14 July 2026 White House release and record what is confirmed.
- Make and document a participation decision with legal sign-off.
- Create a role-based, MFA-protected VINCE account and inventory every token that can read findings.
- Route clearinghouse findings into your existing ISO/IEC 30111 handling process.
- Write a tie-break rule for Gold Eagle, KEV, EPSS and internal priorities.
- Measure triage and remediation times for clearinghouse findings separately.
- Keep OT changes under normal validation and rollback control.
- Track the Cybersecurity Information Sharing Act deadline of 11 December 2026 and any extension.
Standards and references
- The White House: Promoting Advanced Artificial Intelligence Innovation and Security (EO 14409)
- The White House: White House Launches Gold Eagle Initiative
- Cloud Security Alliance: Gold Eagle, the White House's AI Vulnerability Clearinghouse
- Cybersecurity Dive: White House launches Gold Eagle vulnerability clearinghouse
- Nextgov: White House announces Gold Eagle AI clearinghouse for cyber vulnerabilities
- Paul Hastings: White House launches Gold Eagle
- Covington Inside Privacy: White House launches Gold Eagle AI cybersecurity clearinghouse
- Defense One: Industry groups on the cyber sharing law
Related NHI Mgmt Group resources: AI for Vulnerability Discovery and Triage Guide · Bug Bounty and Vulnerability Disclosure Guide · CISA KEV Catalogue Guide · AI Kill Switch Act Guide. This guide summarises Executive Order 14409 and the Gold Eagle programme as of 11 November 2026 and is not legal advice.