Outbrain
Vulnerability disclosure program on security.txt outbrain.com
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 12
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report by email
- https://www.outbrain.com/security/bug-bounty/
- Partial safe harbor
- Some legal protection; read the terms.
- Replies within 3 days
- As the policy promises.
- No public write-ups
- Keep findings private.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Response
-
Within 3 days
First Response │ 3 days
- Safe harbor
-
Partial
Any activities conducted in a manner consistent with this policy will be considered authorized conduct.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
12 assets you may test, 8 excluded.
Domains 10
- api.outbrain.com
- my.outbrain.com
- odb.outbrain.com
- oneapi.zemanta.com
- one.zemanta.com
- outbrain.com
- widgets.outbrain.com
- www.outbrain.com
- www.zemanta.com
- zemanta.com
Android apps 1
- Outbrain Android SDK
iOS apps 1
- Outbrain iOS SDK
Out of scope (8)
- All Flash-related bugs
- Any behavior that is designed by the product and is fully intentional behavior
- Cross-site Request Forgery with minimal security impact
- General best practice concerns
- Issues that do not affect the latest version of modern browsers
- Issues that we are already aware of or have been previously reported
- Missing Security HTTP Headers (without proof of exploitability)
- Those that resolve to third-party services
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Outbrain's policy. "We" in these lines means the program, not this site.
While testing
-
Test vulnerabilities only against accounts that you own or accounts that you have permission from the account holder to test against.
-
Never use a finding to compromise other systems. Use a proof of concept only to demonstrate an issue.
-
Researchers may not engage in any activity that would be disruptive, damaging or harmful to Outbrain, its brands or its users.
-
Do not use automated scanners/tools - these tools include payloads that could trigger state changes or damage production systems and/or data.
-
Before causing damage or potential damage: Stop, report what you've found and request additional testing permission.
-
All supporting evidence and other attachments must be stored only within the report you submit. Do not host any files on external services.
-
Where possible, register accounts using your <username>@wearehackerone.com addresses.
-
Provide your IP address in the bug report.
-
Include a custom HTTP header in all your traffic. Burp and other proxies allow the easy automatic addition of headers to all outbound requests. X-Bug-Bounty: HackerOne-<username>
Not accepted
-
Cross-site Request Forgery with minimal security impact
-
General best practice concerns
-
Missing Security HTTP Headers (without proof of exploitability)
-
All Flash-related bugs
-
Any behavior that is designed by the product and is fully intentional behavior
-
Issues that do not affect the latest version of modern browsers
-
Issues that we are already aware of or have been previously reported
-
Those that resolve to third-party services
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 2 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.