Skip to content

AOL

Bug bounty on Self-hosted aol.com

Accepting reports Full safe harbor
Top reward
Not published
Top severity paid
Not published
Assets in scope
2
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays cash
Amounts are not published; ask before you invest time.
Report by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 5 days
As the policy promises.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

The old policy link stopped working, so we followed the company's security.txt to the current policy.

The policy page has no reward table. Here is what it says, in its own words.

Pays cash
Yes For accepted reports we may provide a financial reward.
Response
Within 5 days We will respond to an accepted report within 5 business days with our evaluation of the report.
Safe harbor
Full As long as you act in good faith, comply with this policy, and applicable laws, we will not take any legal action against you in regard to the report
Hall of fame
Yes In the public information concerning the problem reported, we will give your name as the discoverer of the problem (unless you desire otherwise).

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

2 assets you may test.

Domains 1

  • aol.com

Products and areas 1

  • an AOL service

Rules

What the policy asks of you, and the bug types it won't reward, quoted from AOL's policy. "We" in these lines means the program, not this site.

While testing

  • Do not take advantage of the vulnerability or problem you have discovered.
  • You must not access or attempt to access accounts belonging to other users under any circumstances.
  • Testing must be performed exclusively on accounts that you own.
  • Do not reveal the problem to others until it has been resolved.
  • Do not use attacks on physical security, social engineering, distributed denial of service (or any attack using large volumes of requests), spam, or applications of third parties.
  • Please provide sufficient information to reproduce the problem so we can resolve it as quickly as possible.

Not accepted

  • while we welcome disclosure reports from automated tools/scans, we cannot offer a reward
  • Automated scans are not eligible for rewards.

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 5 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.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.