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

Duke Health

By Duke University and Duke University Health System Vulnerability disclosure program on Self-hosted duke.edu

Accepting reports
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
1
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]
Partial safe harbor
Some legal protection; read the terms.
Replies within 1 day
As the policy promises.
No public write-ups
Keep findings private.

Rewards

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

This program does not pay cash rewards.

Response
Within 1 days ideally within 1 business day
Safe harbor
Partial Duke will not take disciplinary action against Duke faculty, staff, students or others referenced in the Scope section below, in connection with their discovery and immediate reporting to the ITSO/ISO (in good faith and in compliance with this policy and associated procedures) of any suspected Secur

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

Scope

1 asset you may test.

Domains 1

  • duke.edu

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Duke Health's policy.

While testing

  • Any person who wishes to scan for or find Security Vulnerabilities within a Duke system or network must first obtain written permission from the system and network owners.
  • Obtain permission in writing (email is ok) from the system and network owners, and share that information with the IT Security Office.
  • Please do not make any findings (or related research or other documentation) public or share them with anyone until Duke has had a chance to investigate and remediate the reported issues.

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 11 Nov 2026. Last checked 5 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.