Outbound coordinated vulnerability disclosure policy
📰 OpenAI News
OpenAI's outbound coordinated disclosure policy outlines how they report vulnerabilities in third-party software to vendors and open source maintainers
Action Steps
- Identify and validate vulnerabilities through automated and manual code review
- Peer review disclosures for accuracy and reproducibility
- Coordinate disclosures with vendors and open source maintainers through designated reporting channels
- Maintain records and manage vendor interactions
Who Needs to Know This
Security teams and developers at OpenAI and other organizations can benefit from this policy as it promotes responsible disclosure of vulnerabilities and improves ecosystem security
Key Insight
💡 OpenAI's policy emphasizes cooperative and discreet disclosure, with public disclosures only occurring after vendor or open source maintainer consent
Share This
🚨 OpenAI's outbound coordinated disclosure policy prioritizes ecosystem security and responsible vulnerability reporting 💻
Key Takeaways
OpenAI's outbound coordinated disclosure policy outlines how they report vulnerabilities in third-party software to vendors and open source maintainers
Full Article
# Outbound coordinated disclosure policy | OpenAI
[Skip to main content](https://openai.com/policies/outbound-coordinated-disclosure-policy#main)
[](https://openai.com/)
* [Research](https://openai.com/research/index/)
* Products
* [Business](https://openai.com/business/)
* [Developers](https://openai.com/api/)
* [Company](https://openai.com/about/)
* [Foundation(opens in a new window)](https://openaifoundation.org/)
Log in[Try ChatGPT(opens in a new window)](https://chatgpt.com/)
* Research
* Products
* Business
* Developers
* Company
* [Foundation(opens in a new window)](https://openaifoundation.org/)
[Try ChatGPT(opens in a new window)](https://chatgpt.com/)Login
OpenAI
September 22, 2025
# Outbound coordinated disclosure policy
## Purpose
OpenAI is committed to enhancing global software security by responsibly disclosing vulnerabilities discovered in third-party software. This policy governs how OpenAI reports and discloses vulnerabilities we discover in third-party software to vendors and open source maintainers. In these reports we aim to be cooperative, impactful, and maintain high integrity standards.
## Scope
This policy lays out how we disclose issues found in open-source and commercial software through automated and manual code review, as well as discoveries arising from internal usage of third-party software and systems. Detection methods may include:
* AI- or agent-powered application security analysis.
* Security research, audits, and fuzzing of open-source software.
* Evaluations of vendor-supplied or third-party software used within OpenAI operations.
* Other methods as appropriate.
## Principles
**Ecosystem security:** A primary goal is to improve ecosystem security.
**Cooperative:**Good faith, helpful engagements. Third party inbound disclosure processes are respected, subject to exceptions in this policy.
**Discreet by default:**Initial disclosures are private. Public disclosures usually occur only after explicit vendor or open source maintainer consent, subject to exceptions set out below.
**High scale, low friction:** Validated, actionable disclosures are sent.
**Attribution when relevant:**Vulnerabilities will be credited as discovered by OpenAI Security Research - Aardvark. Where applicable, we may attribute discovery to specific individuals, systems, or agents.
## Disclosure workflow
1. Identification and Validation
Upon discovery, each finding is validated for security impact. Reports typically include:
* Impact summary (e.g., denial‑of‑service, memory corruption)
* Affected versions / commit ranges
* Reproduction steps or a proof‑of‑concept (PoC) where possible
* Reproduction aids (e.g., Docker image) where feasible
2. Peer Review
Each disclosure undergoes an internal review process prior to release, including peer review by a security engineer for accuracy, reproducibility, and quality.
* Where a vulnerability is discovered by an automated system, a security engineer reviews the disclosure before it is released.
* Where a vulnerability is discovered by a security engineer, a second security engineer reviews the disclosure.
3. A security program manager coordinates disclosures, maintains records, and manages vendor interactions.
4. Disclosure Process
* **Reporting Channel.** We will generally seek to follow the inbound disclosure procedures of the vendor or open source maintainer who is to receive the disclosure. We reserve the right to follow an alternate procedure at our discretion. Our preferred methods for disclosure include vendor security emails (e.g. the company’s Product Security Incident Response Team email intake), or private GitHub reporting. Submissions to public trackers such as GitHub Issues are avoided by default. We generally will not participate in Bug Bounty programs.
* **Internal Handling.** OpenAI’s outbound disclosure communications are managed through a mailing list d
[Skip to main content](https://openai.com/policies/outbound-coordinated-disclosure-policy#main)
[](https://openai.com/)
* [Research](https://openai.com/research/index/)
* Products
* [Business](https://openai.com/business/)
* [Developers](https://openai.com/api/)
* [Company](https://openai.com/about/)
* [Foundation(opens in a new window)](https://openaifoundation.org/)
Log in[Try ChatGPT(opens in a new window)](https://chatgpt.com/)
* Research
* Products
* Business
* Developers
* Company
* [Foundation(opens in a new window)](https://openaifoundation.org/)
[Try ChatGPT(opens in a new window)](https://chatgpt.com/)Login
OpenAI
September 22, 2025
# Outbound coordinated disclosure policy
## Purpose
OpenAI is committed to enhancing global software security by responsibly disclosing vulnerabilities discovered in third-party software. This policy governs how OpenAI reports and discloses vulnerabilities we discover in third-party software to vendors and open source maintainers. In these reports we aim to be cooperative, impactful, and maintain high integrity standards.
## Scope
This policy lays out how we disclose issues found in open-source and commercial software through automated and manual code review, as well as discoveries arising from internal usage of third-party software and systems. Detection methods may include:
* AI- or agent-powered application security analysis.
* Security research, audits, and fuzzing of open-source software.
* Evaluations of vendor-supplied or third-party software used within OpenAI operations.
* Other methods as appropriate.
## Principles
**Ecosystem security:** A primary goal is to improve ecosystem security.
**Cooperative:**Good faith, helpful engagements. Third party inbound disclosure processes are respected, subject to exceptions in this policy.
**Discreet by default:**Initial disclosures are private. Public disclosures usually occur only after explicit vendor or open source maintainer consent, subject to exceptions set out below.
**High scale, low friction:** Validated, actionable disclosures are sent.
**Attribution when relevant:**Vulnerabilities will be credited as discovered by OpenAI Security Research - Aardvark. Where applicable, we may attribute discovery to specific individuals, systems, or agents.
## Disclosure workflow
1. Identification and Validation
Upon discovery, each finding is validated for security impact. Reports typically include:
* Impact summary (e.g., denial‑of‑service, memory corruption)
* Affected versions / commit ranges
* Reproduction steps or a proof‑of‑concept (PoC) where possible
* Reproduction aids (e.g., Docker image) where feasible
2. Peer Review
Each disclosure undergoes an internal review process prior to release, including peer review by a security engineer for accuracy, reproducibility, and quality.
* Where a vulnerability is discovered by an automated system, a security engineer reviews the disclosure before it is released.
* Where a vulnerability is discovered by a security engineer, a second security engineer reviews the disclosure.
3. A security program manager coordinates disclosures, maintains records, and manages vendor interactions.
4. Disclosure Process
* **Reporting Channel.** We will generally seek to follow the inbound disclosure procedures of the vendor or open source maintainer who is to receive the disclosure. We reserve the right to follow an alternate procedure at our discretion. Our preferred methods for disclosure include vendor security emails (e.g. the company’s Product Security Incident Response Team email intake), or private GitHub reporting. Submissions to public trackers such as GitHub Issues are avoided by default. We generally will not participate in Bug Bounty programs.
* **Internal Handling.** OpenAI’s outbound disclosure communications are managed through a mailing list d
DeepCamp AI