Introducing the OpenAI Safety Bug Bounty program
Summary
OpenAI launched a public Safety Bug Bounty program on March 25, 2026, to identify AI abuse and safety risks across its products. This initiative complements OpenAI's existing Security Bug Bounty by focusing on issues that pose meaningful abuse and safety risks, even if they do not qualify as traditional security vulnerabilities. The program specifically targets agentic risks, including third-party prompt injection, data exfiltration, and unauthorized actions by agentic products. It also covers vulnerabilities exposing OpenAI proprietary information and issues related to account and platform integrity, such as bypassing anti-automation controls or evading account restrictions. While general content-policy bypasses and simple "jailbreaks" are out of scope, the program may consider other flaws leading to direct user harm on a case-by-case basis.
Key takeaway
For AI/ML security teams developing or deploying agentic AI products, your focus should expand beyond traditional cybersecurity to include AI-specific safety and abuse vectors. Actively test for prompt injection, data exfiltration, and unauthorized agent actions, as these represent critical, often overlooked, attack surfaces that can lead to tangible user harm and platform integrity issues.
Key insights
OpenAI's new bug bounty targets AI-specific abuse and safety risks beyond traditional security vulnerabilities.
Principles
- AI safety extends beyond security.
- Reproducibility is key for agentic risks.
- Harm must be plausible and material.
Method
The program accepts submissions for AI-specific safety scenarios like agentic risks (e.g., prompt injection, data exfiltration), exposure of proprietary information, and account/platform integrity issues, triaging them with existing security teams.
In practice
- Report agentic product hijacking.
- Identify proprietary info exposure.
- Flag account integrity bypasses.
Topics
- AI Safety
- Bug Bounty Program
- Prompt Injection
- Agentic AI
- Security Vulnerabilities
Best for: CTO, VP of Engineering/Data, Director of AI/ML, AI Security Engineer, Security Engineer, AI Researcher
Related on AIssential
Editorial summary, takeaway, and curation by AIssential. Original article published by OpenAI News.