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

Rabobank

Bug bounty on security.txt rabobank.com

Accepting reports security.txt
Go to program Website
Top reward
Not published
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.

Pays cash
Amounts are not published; ask before you invest time.
Report by email
https://rabo.nl/o/h1
Partial safe harbor
Some legal protection; read the terms.
No public write-ups
Keep findings private.

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 Therefore in most circumstances, you are eligible for a suitable monetary award.
Safe harbor
Partial If you act in good faith and as per set rules of engagement then there is no reason for Rabobank to report this with Law Enforcement.

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, 8 excluded.

Domains 2

  • rabobank.com
  • rabobank.nl

Products and areas 1

  • Rabobank services
Out of scope (8)
  • Complaints about the service offerings of Rabobank
  • Complaints or questions about the availability of our services
  • Issues considering ATMs (unless they are vulnerabilities)
  • Most of these domains are out of scope
  • Rabobank subdomains that are running third party services
  • Reporting fraud or suspicions of fraud, fake e-mails of phishing e-mails
  • Reporting of issues on SaaS services, subsidiaries and ventures
  • Reporting of viruses or malware

Rules

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

While testing

  • We request you not to publish your report, but share it with our experts and provide them with the time to resolve the issue.
  • Ensure that during your and our investigation of the reported vulnerability, you do not apply any damage
  • Do not utilize social engineering in order to gain access to our IT Systems
  • Your investigation should never disrupt our (online) services
  • Your investigation should never lead to the publicity of bank or customer data
  • Do not place backdoors in systems.
  • Do not apply any changes or delete data in the system
  • Do not attempt to penetrate the system more than required.
  • Do not utilize any brute force techniques (e.g. repeatedly entering passwords) in order to gain access to the system
  • Your investigation should be limited to Rabobank assets only

Not accepted

  • HTTP 404 codes/pages or other HTTP non-200 codes/pages
  • Fingerprinting/version on banner disclosure on common/public services
  • Disclosure of know public files, directories or non-sensitive information (e.g. robots.txt)
  • Clickjacking and issues only exploitable through clickjacking
  • Logout Cross-Site-Request Forgery (Logout CSRF)
  • Presence of application or web browser “autocomplete” or “save password” functionality
  • Lack of Secure/HTTPOnly flags on non-sensitive cookies
  • Weak CAPTCHA or CAPTCHA bypasses
  • Forgot Password page brute force and account lockout not being enforced
  • OPTIONS HTTP method enabled
  • Username/e-mail enumeration through brute force attempts
  • Anything related to HTTP security headers
  • SSL Configuration issues
  • Missing HTTP Public Key Pinning (HPKP)
  • SPF, DKIM, DMARC issues
  • Host Header Injection
  • Content Spoofing/Text Injection on 404 pages
  • Reporting older version of any software without proof of concept or working exploit
  • Information Leakage in Metadata
  • Missing DNSSEC
  • Expired or inactive domains (domain takeovers)
  • Same Site Scripting / localhost DNS record
  • Self XSS
  • Issues depending on outdated browser software
  • Absence of certificate pinning

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