- Top reward
- No cash rewards
- Top severity paid
- Critical
- Assets in scope
- 2
- 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 on HackerOne
- Submit through the program page.
- Replies within 1 day
- As the policy promises.
- No public write-ups
- Keep findings private.
Rewards
What HackerOne lists as the payout for each severity.
This program does not pay cash rewards.
- Response
-
Within 1 days
| First Response | 1 day |
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
2 assets you may test.
Wildcard domains 2
- *.reuters.com Critical No bounty
- *.thomsonreuters.com Critical No bounty
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Thomson Reuters (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.
-
Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
-
When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced).
-
Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
-
Social engineering (e.g. phishing, vishing, smishing) is prohibited.
-
You must avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
-
Hack, penetrate, or otherwise attempt to gain unauthorized access to Thomson Reuters applications, systems, or data in violation of applicable law;
-
Download, copy, disclose or use any proprietary or confidential Thomson Reuters data, including customer data; and
-
Adversely impact Thomson Reuters or the operation of Thomson Reuters applications or systems.
Not accepted
-
Clickjacking on pages with no sensitive actions
-
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
-
Attacks requiring MITM or physical access to a user's device.
-
Previously known vulnerable libraries without a working Proof of Concept.
-
Comma Separated Values (CSV) injection without demonstrating a vulnerability.
-
Missing best practices in SSL/TLS configuration.
-
Any activity that could lead to the disruption of our service (DoS).
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
-
Rate limiting or brute-force issues on non-authentication endpoints
-
Missing best practices in Content Security Policy.
-
Missing HttpOnly or Secure flags on cookies
-
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
-
Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
-
Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
-
Tabnabbing
-
Open redirect - unless an additional security impact can be demonstrated
-
Issues that require unlikely user interaction
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 56 minutes 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.
Original policy
Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
At Thomson Reuters, we take cybersecurity seriously and value the contributions of the security community at large. The responsible disclosure of potential issues helps us ensure the security and privacy of our customers and data.
Response Targets
Thomson Reuters will make best efforts to meet the following response timelines for researchers participating in our program:
| Type of Response | in Business Days |
|---|---|
| First Response | 1 day |
| Time to Triage | 2 days |
| Time to Resolution | Depends on severity & complexity |
We’ll try to keep you informed about our progress throughout the process.
Scope
Some of the assets under *.thomsonreuters.com may be third-party systems not owned by Thomson Reuters. Reports on these assets will fall out of scope for this program upon triage by Thomson Reuters PSIRT and researchers will be allowed to self-close these reports.
Disclosure Policy
- Please do not discuss this program or any reported vulnerabilities (even if resolved) outside of the program without express consent from the organization.
- Follow HackerOne's disclosure guidelines.
Program Rules
If you believe you’ve found a security issue in one of our products or services, please send it to us and include the following details with your report:
- Provide a description of the issue and where it is located.
- Provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.
- Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
- When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced).
- Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
- Social engineering (e.g. phishing, vishing, smishing) is prohibited.
- You must avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
The following are examples of prohibited activities:
- Hack, penetrate, or otherwise attempt to gain unauthorized access to Thomson Reuters applications, systems, or data in violation of applicable law;
- Download, copy, disclose or use any proprietary or confidential Thomson Reuters data, including customer data; and
- Adversely impact Thomson Reuters or the operation of Thomson Reuters applications or systems.
Thomson Reuters does not waive any rights or claims with respect to such activities.
Out of Scope Vulnerabilities
When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
- Clickjacking on pages with no sensitive actions
- Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
- Attacks requiring MITM or physical access to a user's device.
- Previously known vulnerable libraries without a working Proof of Concept.
- Comma Separated Values (CSV) injection without demonstrating a vulnerability.
- Missing best practices in SSL/TLS configuration.
- Any activity that could lead to the disruption of our service (DoS).
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
- Rate limiting or brute-force issues on non-authentication endpoints
- Missing best practices in Content Security Policy.
- Missing HttpOnly or Secure flags on cookies
- Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
- Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
- Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
- Tabnabbing
- Open redirect - unless an additional security impact can be demonstrated
- Issues that require unlikely user interaction
Thank you for helping keep Thomson Reuters and our users safe!