Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

The Telegraph

Vulnerability disclosure program on security.txt telegraph.co.uk

Accepting reports security.txt
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
1
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://telegraph.co.uk/help/vulnerability-disclosure
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.

Pays cash
No This is a vulnerability disclosure program and not a bug bounty.

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

Scope

1 asset you may test.

Domains 1

  • telegraph.co.uk

Rules

What the policy asks of you, and the bug types it won't reward, quoted from The Telegraph's policy.

While testing

  • Limit your report to the most serious vulnerability.
  • If reporting subdomain takeover, report all related subdomains in the same report and do not provision the subdomain yourself or publish anything to the subdomain.
  • If reporting cross-site scripting, provide the browser name, version and platform.
  • You must comply with all applicable laws.
  • Access unnecessary, excessive or significant amounts of data.
  • Modify data in the Organisation’s systems or services.
  • Use high-intensity invasive or destructive scanning tools to find vulnerabilities.
  • Disrupt the Organisation’s services or systems.
  • Communicate any vulnerabilities or associated details other than by means described in the published security.txt.
  • Social engineer, ‘phish’ or physically attack the Organisation’s staff or infrastructure.

Not accepted

  • Submit reports detailing TLS configuration weaknesses, for example “weak” cipher suite support or the presence of TLS1.0 support.
  • Attempt or report any form of denial of service, e.g. overwhelming a service with a high volume of requests.

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.

Search NVD

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