AIToday
Large Language ModelsAI Business & IndustryOpenAI BlogPublished: Mar 26, 2026, 04:29 JST

OpenAI launches Safety Bug Bounty program

OpenAI launches Safety Bug Bounty program

3 Key Points

  1. What happened

    OpenAI today launched a public Safety Bug Bounty program to identify AI abuse and safety risks across its products, complementing its existing Security Bug Bounty.

  2. Why it matters

    The program targets issues that fall outside conventional security vulnerabilities but still pose real risks, such as agentic prompt injection and data exfiltration, aiming to prevent tangible harm from AI misuse.

  3. What to watch

    The program's effectiveness hinges on whether researchers can reliably reproduce third-party prompt injection and data exfiltration at least 50% of the time, with submissions triaged by OpenAI's Safety and Security Bug Bounty teams.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The launch of the Safety Bug Bounty reflects OpenAI's recognition that AI safety risks extend beyond traditional security flaws. While the Security Bug Bounty covers conventional vulnerabilities, this new program addresses issues like third-party prompt injection, where attacker text can hijack an AI agent to perform harmful actions or leak sensitive data—a risk growing with the rise of agentic products. By inviting researchers to report such issues, OpenAI aims to catch problems that automated testing might miss.

The program's scope is carefully defined: agentic risks must be reliably reproducible, and reports must indicate plausible material harm. Jailbreaks, such as those causing rude language, are out of scope. This structure suggests OpenAI is focusing on concrete, high-impact risks rather than general content-policy bypasses.

The stakes center on the program's ability to surface actionable vulnerabilities. Its success hinges on whether the community can provide reproducible examples of abuse, which could inform future safeguards. This initiative likely signals a broader industry shift toward proactive, researcher-driven safety testing as AI capabilities expand.

FAQ
What types of issues are in scope for the Safety Bug Bounty?
In-scope issues include agentic risks (e.g., prompt injection and data exfiltration), leaks of OpenAI proprietary information, and account/platform integrity vulnerabilities. Jailbreaks are generally out of scope, except for private campaigns on certain harm types.
How does this program relate to the existing Security Bug Bounty?
The Safety Bug Bounty complements the Security Bug Bounty by accepting issues that pose meaningful abuse and safety risks even if they don't meet security vulnerability criteria. Submissions may be rerouted between the two programs as appropriate.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleNormal Computing secures $50M Samsung investment to develop GPU alternatives addressing AI's escalating computational and energy costs