- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 7
- Public CVEs
- 0
- Last change
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
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 1 day
- 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.
This program does not pay cash rewards.
- Pays cash
-
No
Unfortunately, due to the BBC's funding structure, it is not currently possible for us to offer a paid bug bounty programme.
- Response
-
Within 1 days
you will receive an acknowledgement reply email from the BBC Security Team, this is usually within 24 hours of your report being received.
- Safe harbor
-
Full
The BBC will not seek prosecution of any security researcher who reports, in good faith and in accordance with this policy, any security vulnerability on an in-scope BBC service.
- Hall of fame
-
Yes
We will also offer to include reporters of qualifying vulnerabilities on our acknowledgments page and we'll ask for the details you wish to be included.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
7 assets you may test, 12 excluded.
Domains 5
- bbc.com
- bbc.co.uk
- domain that has a security.txt file in its root
- github.com
- shop.bbc.com No bounty
Source code 1
- https://github.com/bbc/
Wildcard domains 1
- subdomains are considered in scope provided their parent domain is in scope
Out of scope (12)
- broken link hijacking where the linked page is not actively malicious
- Clickjacking vulnerabilities
- CRLF attacks where the resulting impact is minimal
- CSRF where the resulting impact is minimal
- Host header injection where the resulting impact is minimal
- improper session management / session fixation vulnerabilities
- Issues surrounding the verification of email addresses used to create user accounts
- missing security headers or suboptimal email-related configurations such as SPF, DMARC etc.
- Network data enumeration techniques
- Self XSS
- TLS configuration weaknesses
- Volumetric/Denial of Service vulnerabilities
Rules
What the policy asks of you, and the bug types it won't reward, quoted from BBC's policy. "We" in these lines means the program, not this site.
While testing
-
Access unnecessary amounts of data.
-
Violate the privacy of BBC users, staff, contractors, systems etc.
-
Communicate any vulnerabilities or associated details via methods not described in this policy
-
Modify data in our systems/services which is not your own;
-
Disrupt our service(s) and/or systems; or
-
Disclose any vulnerabilities in BBC systems/services to 3rd parties/the public prior to the BBC confirming that those vulnerabilities have been mitigated or rectified.
-
We request that any and all data retrieved during research is securely deleted as soon as it is no longer required and at most, 1 month after the vulnerability is resolved
Not accepted
-
Volumetric/Denial of Service vulnerabilities
-
TLS configuration weaknesses
-
missing security headers or suboptimal email-related configurations such as SPF, DMARC etc.
-
Issues surrounding the verification of email addresses used to create user accounts
-
Clickjacking vulnerabilities
-
Self XSS
-
CSRF where the resulting impact is minimal
-
CRLF attacks where the resulting impact is minimal
-
Host header injection where the resulting impact is minimal
-
Network data enumeration techniques
-
improper session management / session fixation vulnerabilities
-
broken link hijacking where the linked page is not actively malicious
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.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Scope
− https://github.com/bbc/REPO_NAME_HERE/security/policy, − security.md
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.