Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Heidi Health Pty Ltd

Bug bounty on security.txt heidihealth.com

Accepting reports Full safe harbor KYC to get paid security.txt
Go to program Website
Top reward
Not published
Top severity paid
Not published
Assets in scope
5
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays cash
Amounts are not published; ask before you invest time.
Report by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 2 days
As the policy promises.
Paid by Airwallex
Proof of identity needed to get paid.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

The policy page has no reward table. Here is what it says, in its own words.

Pays cash
Yes In rare cases we may make a discretionary payment; this is solely at Heidi Health's discretion and never an obligation.
Response
Within 2 days We aim to respond within 2 business days.
Safe harbor
Full Heidi Health will not pursue civil or criminal action, and will not refer matters to law enforcement, against any individual who:
Hall of fame
Yes Valid reports are recognised publicly on our Security Researcher Acknowledgments page.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

5 assets you may test, 13 excluded.

Domains 2

  • app.heidihealth.com
  • heidihealth.com

Hardware and IoT 1

  • Heidi Remote products

Products and areas 2

  • Heidi Health AI features
  • Heidi Health web and mobile applications
Out of scope (13)
  • Any testing conducted on live patient data or production systems without explicit written permission
  • Automated scanning without prior written approval
  • Denial of service (DoS/DDoS) attacks
  • General enumeration of user IDs or resource identifiers where no data is accessed or compromised.
  • Issues in software versions that are explicitly end-of-life
  • Missing security headers, unless an exploitable impact can be demonstrated.
  • Other users' accounts
  • Physical security vulnerabilities
  • Self-XSS (Cross-Site Scripting that cannot affect other users), or vulnerabilities requiring unlikely user interaction.
  • Social engineering or phishing of Heidi Health employees
  • Systems containing real patient data
  • Testing third-party integrations (e.g. identity providers, payment processors, partner APIs)
  • Vulnerabilities in third-party services not under our control

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Heidi Health Pty Ltd's policy. "We" in these lines means the program, not this site.

While testing

  • Always test against your own account in the production environment, or request access to a dedicated test environment.
  • Automated or scripted scanning of any Heidi Health system without prior written approval.
  • Accessing, downloading, or retaining data belonging to any other user, patient, or organisation, even if access is technically possible
  • Modifying, deleting, or corrupting any data or system state, including your own account data if doing so could affect system integrity
  • Exploiting a vulnerability beyond what is necessary to confirm it exists.
  • Exfiltrating or storing sensitive data encountered during testing.
  • Using automated tools to brute-force credentials, API keys, tokens, or resource identifiers
  • Please do not include actual patient data, credentials, or any other sensitive personal information in your report.
  • Demand payment before disclosing, or threaten disclosure to extract a payment

Not accepted

  • Denial of service (DoS/DDoS) attacks
  • Social engineering or phishing of Heidi Health employees
  • Physical security vulnerabilities
  • Vulnerabilities in third-party services not under our control
  • Issues in software versions that are explicitly end-of-life
  • Automated scanning without prior written approval
  • Missing security headers, unless an exploitable impact can be demonstrated.
  • Self-XSS (Cross-Site Scripting that cannot affect other users), or vulnerabilities requiring unlikely user interaction.
  • General enumeration of user IDs or resource identifiers where no data is accessed or compromised.
  • Any testing conducted on live patient data or production systems without explicit written permission

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 2 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.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.