- Top reward
- $5,000
- Top severity paid
- Critical
- Assets in scope
- 6
- Public CVEs
- 14
- Last change
At a glance
What to know before you start testing.
- Pays up to $5,000
- for critical bugs.
- Report on HackerOne
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 5 days
- As the policy promises.
- No public write-ups
- Keep findings private.
Rewards
What HackerOne lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$5,000 from $2,500 |
| High |
|
$2,500 from $1,000 |
| Medium |
|
$750 from $500 |
| Low |
|
$500 from $100 |
- Response
-
Within 5 days
| First Response | 5 days |
- Safe harbor
-
Full
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
6 assets you may test, 4 excluded.
Desktop and binaries 2
- HyprUnlock.exe Critical
- HYPR Workforce Access.app Critical
Wildcard domains 2
- *.gethypr.com Critical
- *.hypr.com Critical
Android apps 1
- com.hypr.one Critical
iOS apps 1
- com.hypr.one Critical
Out of scope (4)
- demo.hypr.com
- help.hypr.com
- partners.hypr.com
- support.hypr.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from HYPR (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Test only against tenants you own or that have been assigned to you.
-
Testing against production or customer tenants is not permitted and may disqualify the report.
-
Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
-
Social engineering (e.g. phishing, vishing, smishing) is prohibited.
-
Make a good faith effort to 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.
-
Please do not delete any data that's already in the platform.
-
Please provide detailed reports with reproducible steps.
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.
-
User enumeration of any kind.
-
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 bruteforce issues
-
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
-
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
-
CVEs without a working exploit or when no sensitive info is retrieved (i.e.: CVE-2020-10770)
-
Vulnerabilities affecting older tenant versions.
-
Self-XSS and issues requiring the victim to paste attacker-supplied content into their own browser or client.
-
Issues requiring local administrator privileges on the victim's machine.
-
Missing security headers without a demonstrated attack.
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 17 minutes 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.
-
Rules updated
Added: “A report submitted as Critical or High that turns out not to be a vulnerability will be closed as Not Applicable. Period.”
-
Rules updated
Added: “Main subdomain for testing: **https://hypr29170.gethypr.com/** or **https://pentesting.gethypr.com/”
-
Scope added
demo.hypr.com (out of scope)
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
| CVE | Summary | Severity | Published |
|---|---|---|---|
| CVE-2026-2414 | Authorization bypass through User-Controlled key vulnerability in HYPR Server allows Privilege Escalation.This issue affects Server: from 9.5.2 before 10.7.2. | Medium 5.6 | 25 Mar 2026 |
| CVE-2024-8273 | Authentication Bypass by Spoofing vulnerability in HYPR Server allows Identity Spoofing.This issue affects Server: before 10.1. | High 7.1 | 11 Dec 2025 |
| CVE-2024-0068 | Improper Link Resolution Before File Access ('Link Following') vulnerability in HYPR Workforce Access on MacOS allows File Manipulation.This issue affects Workforce Access: before 8.7.1. | Medium 5.5 | 29 Feb 2024 |
| CVE-2023-6336 | Improper Link Resolution Before File Access ('Link Following') vulnerability in HYPR Workforce Access on MacOS allows User-Controlled Filename.This issue affects Workforce Access: before 8.7. | High 7.2 | 16 Jan 2024 |
| CVE-2023-5097 | Improper Input Validation vulnerability in HYPR Workforce Access on Windows allows Path Traversal.This issue affects Workforce Access: before 8.7. | High 7.0 | 16 Jan 2024 |
| CVE-2023-6334 | Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in HYPR Workforce Access on Windows allows Overflow Buffers.This issue affects Workforce Access: before 8.7. | Medium 5.3 | 16 Jan 2024 |
| CVE-2023-6335 | Improper Link Resolution Before File Access ('Link Following') vulnerability in HYPR Workforce Access on Windows allows User-Controlled Filename.This issue affects Workforce Access: before 8.7. | Medium 6.4 | 16 Jan 2024 |
| CVE-2023-1837 | Missing Authentication for critical function vulnerability in HYPR Server allows Authentication Bypass when using Legacy APIs.This issue affects HYPR Server: before 8.0 (with enabled Legacy APIs) | High 8.5 | 23 May 2023 |
| CVE-2023-0834 | Incorrect Permission Assignment for Critical Resource vulnerability in HYPR Workforce Access on MacOS allows Privilege Escalation.This issue affects Workforce Access: from 6.12 before 8.1. | High 7.0 | 28 Apr 2023 |
| CVE-2023-1477 | Improper Authentication vulnerability in HYPR Keycloak Authenticator Extension allows Authentication Abuse.This issue affects HYPR Keycloak Authenticator Extension: before 7.10.2, before 8.0.3. | High 7.2 | 28 Apr 2023 |
| CVE-2022-3258 | Incorrect Permission Assignment for Critical Resource vulnerability in HYPR Workforce Access on Windows allows Authentication Abuse. | Low 3.7 | 3 Nov 2022 |
| CVE-2022-2192 | Forced Browsing vulnerability in HYPR Server version 6.10 to 6.15.1 allows remote attackers with a valid one-time recovery token to elevate privileges via path tampering in the Magic Link page. This issue affects: HYPR Server versions later than 6.10; version 6.15.1 and prior versions. | High 7.5 | 19 Jul 2022 |
| CVE-2022-2193 | Insecure Direct Object Reference vulnerability in HYPR Server before version 6.14.1 allows remote authenticated attackers to add a FIDO2 authenticator to arbitrary accounts via parameter tampering in the Device Manager page. This issue affects: HYPR Server versions prior to 6.14.1. | High 7.5 | 19 Jul 2022 |
| CVE-2022-1984 | This issue affects: HYPR Windows WFA versions prior to 7.2; Unsafe Deserialization vulnerability in HYPR Workforce Access (WFA) before version 7.2 may allow local authenticated attackers to elevate privileges via a malicious serialized payload. | Medium 4.5 | 19 Jul 2022 |
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.
Bug Bounty Test Request Form
In order to request credentials for the HYPR platform please submit your handle and email in this form.
Main subdomain for testing: https://hypr29170.gethypr.com/ or https://pentesting.gethypr.com/
Additional subdomain to test against cross-tenant access: https://pentesting2.gethypr.com/ / https://hypr46478.gethypr.com/. Valid user for this tenant: [email protected]
Other subdomains may be running older HYPR versions and bounties might not be applicable as described on this policy.
You will receive an invitation email from HYPR to create an account. Please note you'll need to install the HYPR app from Google Play or App Store in order to create an account and login to our web platform, alternatively you can use passkeys to register and login. The invitation email includes the links to download the proper app for your phone.
An admin account will be created for you and you can add as many users as you'd like once you create your first account.
Please do not delete any data that's already in the platform. You can edit and delete any data that you add but please don't delete anything previous since this is a shared environment.
Treasure map / getting started
Please review the attached pdf that contains a quick-start guide as well as what our main security concerns are: F1872893
Our Mission
We have one mission and that is to create a passwordless world. For us, security isn’t just about keeping the bad guys out. It’s about protecting people in everything they do, wherever they are.
HYPR founders realized passwords will continue to be the hackers’ favorite target unless something is done about it. They saw it as an opportunity to approach security in a brand new way. What if our everyday smartphone can be used to change the security and user experience landscape? That became the launching pad for HYPR.
Our global team comes from software, information security, and digital identity backgrounds to deliver security that’s meant for everyone. United by the common mission to create a passwordless world, we maintain a work ethic that prioritizes our customer’s success and growth.
HYPR looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.
Response Targets
HYPR will make a best effort to meet the following SLAs for hackers participating in our program. Please expect responses Monday through Friday during EST business hours:
| Type of Response | SLA in business days |
|---|---|
| First Response | 5 days |
| Time to Triage | 10 days |
| Time to Bounty | 60 days |
| Time to Resolution | depends on severity and complexity |
We’ll try to keep you informed about our progress throughout the process.
Disclosure Policy
- Please do not discuss any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
- Follow HackerOne's disclosure guidelines.
Program Rules
- Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
- Test only against tenants you own or that have been assigned to you. Testing against production or customer tenants is not permitted and may disqualify the report.
- Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
- When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
- Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
- Same vulnerability being present across different tenants will be awarded one bounty.
- Social engineering (e.g. phishing, vishing, smishing) is prohibited.
- Make a good faith effort to 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.
- Use of AI tooling to find or write up issues is allowed. We only ask that reports stay concise. Long generated narratives slow triage down and do not increase severity. You are responsible for validating anything a tool produced before submitting it.
- A report submitted as Critical or High that turns out not to be a vulnerability will be closed as Not Applicable. Period.
- Access control reports are validated with our product team before we make a call. Access may be intended even when it is not exposed in the UI, so these reports can take longer to resolve.
Rewards
Our rewards are based on severity per CVSS (the Common Vulnerability Scoring Standard). Please note these are general guidelines, and reward decisions are up to the discretion of HYPR.
Documentation
All documentation for the HYPR platform is located at the HYPR Docs Website.
Scoped Applications
You can download these applications directly from their appropriate application stores.
- iOS application at App Store: com.hypr.one
- Android application at Google Play Store: com.hypr.one
- Desktop applications can be downloaded from the platform.
Out of scope domains
support.hypr.com help.hypr.com partners.hypr.com
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.
- Vulnerabilities already identified internally before your report, whether or not a fix is scheduled or shipped.
- 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.
- User enumeration of any kind.
- 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 bruteforce issues
- 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).
- Public Zero-day vulnerabilities will be awarded on a case by case basis.
- Tabnabbing
- Open redirect - unless an additional security impact can be demonstrated
- Issues that require unlikely user interaction
- CVEs without a working exploit or when no sensitive info is retrieved (i.e.: CVE-2020-10770)
- In Scope exploited Stale DNS entries will be awarded a $250 bounty
- Vulnerabilities affecting older tenant versions.
- Vulnerabilities related to fully managed third-party services will be awarded on a case by case basis, even if these are under a HYPR DNS entry. i.e.: status.hypr.com, etc
- Self-XSS and issues requiring the victim to paste attacker-supplied content into their own browser or client.
- Issues requiring local administrator privileges on the victim's machine.
- Missing security headers without a demonstrated attack.
- Demo, sample, and reference integrations, including our sample SDK applications and demonstration sites. These are integration examples, not production services. Reports against them are accepted but rated on the sample application's own impact, not on the impact the same bug would have in the platform.
Safe Harbor
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
Thank you for helping keep HYPR and our users safe!