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

Utrecht University

Vulnerability disclosure program on security.txt uu.nl

Accepting reports Full safe harbor security.txt
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
3
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]
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 5 days
As the policy promises.
Publish after a fix
Coordinate the timing with the company.

Rewards

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

This program does not pay cash rewards.

Pays cash
No Our Responsible Disclosure program does not provide financial rewards or bug bounties.
Response
Within 5 days We will respond to your report within five working days with our assessment of the report and the date the issue is expected to be resolved.
Safe harbor
Full We will not consider any legal steps against those who notified us and who gained unauthorised access to sensitive information if they have complied with the above points.
Hall of fame
Yes If you so wish, we will include you as a reporter in the Hall of Fame, under a pseudonym if you want.

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

Scope

3 assets you may test, 19 excluded.

Domains 3

  • students.uu.nl/it No bounty
  • student website (it) No bounty
  • uu.nl
Out of scope (19)
  • Anything related to HTTP/XML security headers
  • Authentication for public FTP mirrors for open-source projects
  • Best practices recommendations or hardening measures without a demonstrable impact on the confidentiality, integrity or availability of our systems or data
  • Clickjacking and issues only exploitable through clickjacking
  • Disclosure of known public files or directories or non-sensitive information (e.g. robots.txt)
  • Disclosure of publicly available software and/or source code
  • Expired or otherwise misconfigured SSL/TLS certificates, unless it can be demonstrated that they result in a security risk
  • Fingerprint version banner disclosure on common/public services
  • Host header injection
  • HTTP 404 codes/pages or other HTTP non-200 codes/pages and content spoofing/text injection on these pages
  • Information leaks in metadata
  • Issues with mixed-content warnings
  • Issues with the HTTP 'referer' header
  • Lack of secure/HTTP-only flags on non-sensitive cookies
  • Missing limits on login attempts
  • OPTIONS HTTP method enabled
  • Reporting older versions of any software without proof of concept or working exploit
  • SPF, DKIM, DMARC issues
  • SSL Configuration Issues

Rules

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

While testing

  • Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying any data.
  • Do not reveal the problem to others until it has been resolved.
  • Do not use attacks on physical security, social engineering, (distributed) denial of service or spam. Do not attack third-party applications.
  • Do not use automated tools to run large-scale tests on our websites and applications.
  • Provide sufficient information for us to reproduce the problem, so we will be able to resolve it as quickly as possible.

Not accepted

  • trivial vulnerabilities or bugs that cannot be abused
  • Authentication for public FTP mirrors for open-source projects
  • Disclosure of publicly available software and/or source code
  • HTTP 404 codes/pages or other HTTP non-200 codes/pages and content spoofing/text injection on these pages
  • Fingerprint version banner disclosure on common/public services
  • Missing limits on login attempts
  • Disclosure of known public files or directories or non-sensitive information (e.g. robots.txt)
  • Clickjacking and issues only exploitable through clickjacking
  • Lack of secure/HTTP-only flags on non-sensitive cookies
  • OPTIONS HTTP method enabled
  • Issues with the HTTP 'referer' header
  • Issues with mixed-content warnings
  • Anything related to HTTP/XML security headers
  • SSL Configuration Issues
  • Host header injection
  • Expired or otherwise misconfigured SSL/TLS certificates, unless it can be demonstrated that they result in a security risk
  • SPF, DKIM, DMARC issues
  • Reporting older versions of any software without proof of concept or working exploit
  • Information leaks in metadata
  • Best practices recommendations or hardening measures without a demonstrable impact on the confidentiality, integrity or availability of our systems or data

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