The Royal Household
Vulnerability disclosure program on security.txt royal.uk
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 3
- 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
- [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.
This program does not pay cash rewards.
- Response
-
Within 5 days
we will respond to your report within 5 working days
- Safe harbor
-
Full
The Royal Household will not seek prosecution of any security researcher who reports any security vulnerability in a Royal Household service or system where the researcher has acted in good faith and in accordance with this disclosure policy.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
3 assets you may test.
Domains 2
- royal.gov.uk
- royal.uk
Products and areas 1
- any publicly accessible Royal Household website, system, application or infrastructure
Rules
What the policy asks of you, and the bug types it won't reward, quoted from The Royal Household's policy.
While testing
-
Break any applicable laws or regulations.
-
Communicate any vulnerabilities or associated details other than by means described in the published security.txt.
-
Use high-intensity invasive or destructive technical security scanning tools, that could impact the quality of service of Royal Household infrastructure or services, to find vulnerabilities.
-
Engage in physical testing of facilities or resources or perform social engineering on The Royal Household.
-
Attempt or report any form of denial of service, for example, overwhelming a service with high volume requests.
-
Submit reports detailing TLS configuration weaknesses, for example “weak” cipher suite support or the presence of TLS 1.0 support.
-
Demand financial compensation before or after disclosing any vulnerabilities.
-
Always comply with data protection rules and must not violate the privacy of The Royal Household users, staff, contractors, services, or systems.
-
Conform to the HackerOne Code of Conduct: https://www.hackerone.com/policies/code-of-conduct
Not accepted
-
TLS configuration weaknesses, for example “weak” cipher suite support or the presence of TLS 1.0 support
-
any form of denial of service
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 12 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.