Met Office
Vulnerability disclosure program on security.txt metoffice.gov.uk
- 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.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 3 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.
This program does not pay cash rewards.
- Pays cash
-
No
Unfortunately, due to the Met Office’s funding structure, it is not currently possible for us to offer a paid bug bounty programme.
- Response
-
Within 3 days
After you contact the Met Office, you will receive an acknowledgement reply usually within three working days of your report being received.
- Safe harbor
-
Full
The Met Office affirms that it will not seek prosecution of any security researcher who reports any security vulnerability on a Met Office service or system, where the researcher has acted in good faith and in accordance with this policy.
- Hall of fame
-
Yes
Where a report qualifies and where possible, we will offer kudos via the HackerOne platform.
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
- metoffice.gov.uk
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Met Office's policy. "We" in these lines means the program, not this site.
While testing
-
access unnecessary amounts of data. For example, 2 or 3 records is enough to demonstrate most vulnerabilities, such as an enumeration or direct object reference vulnerability;
-
use high-intensity invasive or destructive technical security scanning tools to find vulnerabilities;
-
violate the privacy of Met Office users, staff, contractors, services or systems. For example by sharing, redistributing and/or not properly securing data retrieved from our systems or services;
-
communicate any vulnerabilities or associated details using methods not described in this policy, or with anyone other than their assigned Met Office security contact;
-
modify data in Met Office systems or services which does not belong to the researcher;
-
disrupt Met Office services or systems;
-
social engineer, ‘phish’ or physically attack Met Office staff or infrastructure;
-
disclose any vulnerabilities in Met Office systems or services to third parties or the public, prior to the Met Office confirming that those vulnerabilities have been mitigated or rectified;
-
require financial compensation in order to disclose any vulnerabilities (such as holding an organisation to ransom).
-
We ask you to delete securely any and all data retrieved during your research as soon as it is no longer required or within one month of the vulnerability being resolved, whichever occurs first.
Not accepted
-
volumetric vulnerabilities are not in scope - meaning that simply overwhelming a service with a high volume of requests is not in scope
-
TLS configuration weaknesses, for example “weak” cipher suite support or the presence of TLS1.0 support, are not in scope
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 3 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.