Unisys Managed Bug Bounty Engagement
By Unisys Bug bounty on Bugcrowd unisys.com
- Top reward
- $4,500
- Top severity paid
- Critical
- Assets in scope
- 2
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to $4,500
- for critical bugs, from $50.
- Report on Bugcrowd
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- No public write-ups
- Keep findings private.
Rewards
What Bugcrowd lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$4,500 from $3,000 |
| High |
|
$2,000 from $1,000 |
| Medium |
|
$500 from $250 |
| Low |
|
$100 from $50 |
- Safe harbor
-
Full
Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy;
Summarised with AI from the program policy on Bugcrowd, read 12 Nov 2026, and checked word for word against it. Read the original
Earlier reward tables (1)
- 11 Nov 2026 to 11 Nov 2026: Critical up to $4,500
Scope
2 assets you may test.
Web 2
- http://unifysquare.com
- http://unisys.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Unisys Managed Bug Bounty Engagement (via Bugcrowd)'s policy.
While testing
-
Testing is only authorized on the targets listed as in scope.
-
Please add the following header to your HTTP traffic to prevent interruptions and verify non-malicious behavior: X-Bugcrowd:<bugcrowdusername>
-
All vulnerabilities must be reported exclusively through the Bugcrowd platform.
-
If you believe you've identified a vulnerability that may lead to post-exploitation activity including modification or destruction of data please stop testing and submit your finding.
Not accepted
-
P5 vulnerabilities
-
DoS/DDoS/Network DoS
-
Rate limiting bypass attempts
-
Email bombing flooding
-
Issues with corresponding patches that are younger than 60 days
-
User Enumeration
-
Concurrent login caching API calls
-
Session validation after password reset or change
-
Subdomain Takeover
-
Stealer Logs
-
Social engineering attacks
-
Phishing attacks
-
Physical attacks
Summarised with AI from the program policy on Bugcrowd, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 1 hour 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.
-
Status
Program status changed
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 bugcrowd.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Description
We are a global technology solutions company that powers breakthroughs for the world’s leading organizations. These solutions — digital workplace, cloud, applications & infrastructure, enterprise computing and business process solutions — help people overcome obstacles and not only reach their greatest potential but go beyond it. No technology is perfect and Unisys believes that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. We are excited for you to participate as a security researcher to help us identify vulnerabilities in our assets. Good luck, and happy hunting! Ratings/Rewards: For the initial prioritization/rating of findings, this program will use the Bugcrowd Vulnerability Rating Taxonomy . However, it is important to note that in some cases a vulnerability priority will be modified due to its likelihood or impact. In any instance where an issue is downgraded, a full, detailed explanation will be provided to the researcher - along with the opportunity to appeal, and make a case for a higher priority.
Targets
Testing is only authorized on the targets listed as in scope. Any domain/property of Unisys not listed in the targets section is out of scope for this program. This includes any/all subdomains not listed above. While we have identified these assets as the primary targets, we understand that our digital footprint may extend beyond this list. Therefore, we welcome researchers to identify and report vulnerabilities in other Unisys-owned assets in our VDP , as long as they fall under our ownership and are not explicitly excluded from the program. However, be aware that it is ineligible for rewards or points-based compensation. Access All of the targets are accessible via the public internet and available Traffic Identification Please add the following header to your HTTP traffic to prevent interruptions and verify non-malicious behavior: X-Bugcrowd: Eligibility All vulnerabilities must be reported exclusively through the Bugcrowd platform. Participants must not be residents of countries under any trade restrictions or sanctions. Employees of Unisys and their immediate family members are not eligible for rewards. Excluded Submission Types The following submissions are excluded from this program, but can be considered for our VDP . P5 vulnerabilities Availability/volumetric testing e.g.: DoS/DDoS/Network DoS Rate limiting bypass attempts Email bombing flooding Issues with corresponding patches that are younger than 60 days User Enumeration Concurrent login caching API calls Session validation after password reset or change Subdomain Takeover Stealer Logs N-day/Third party 0-day Policy When N-Day bugs are released to the public, we will consider these as in scope after 30 days has gone by e.g: N-day released on 01/01/2025, we would consider it in-scope on 31/01/2025 Out of Scope Interacting or manipulate other stakeholders and their associated accounts including: Social engineering attacks Phishing attacks Physical attacks Third party providers and services Any subdomain that redirects to non-unisys domain will be considered out of scope. We will consider the cross-site scripting issue in gls*.*.unisys as low severity. Any submissions pertaining to WSO2 products will be considered out of scope and will not be eligible for bounty. Potential post-exploitation scenarios : If you believe you've identified a vulnerability that may lead to post-exploitation activity including modification or destruction of data please stop testing and submit your finding. We will work with you to evaluate the vulnerability and award you accordingly for the final impact and severity. Safe Harbor: When conducting vulnerability research according to this policy, we consider this research to be: Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy; Exempt from the Digital Millennium Copyright Act (DMCA), and we will not bring a claim against you for circumvention of technology controls; Exempt from restrictions in our Terms & Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis for work done under this policy; and Lawful, helpful to the overall security of the Internet, and conducted in good faith. You are expected, as always, to comply with all applicable laws. If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please create a ticket with Bugcrowd Support for clarification before proceeding.