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

Eurofins

Vulnerability disclosure program on security.txt eurofins.com

Accepting reports security.txt
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.
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.

Pays cash
No Eurofins does not operate a bug bounty and does not pay any bounties.
Safe harbor
Partial Make a good faith effort to avoid privacy violations (incl. any personal data protection breaches), destruction of data, and interruption or degradation of our service.
Hall of fame
Yes Eurofins runs a Hall of Fame where we express our sincere thanks to security researchers who ethically report security issues to us.

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

Domains 1

  • eurofins.com
Out of scope (30)
  • API keys found in our mobile applications.
  • Attacks requiring physical access to a user's device or attacks requiring MITM.
  • Certain reports of spam.
  • Clickjacking without an impact.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Content spoofing / reflection / injection (on 404 page, search result page etc.) unless executes code.
  • Cookie and logout policies.
  • Email enumeration.
  • Exposed credentials that are either no longer valid, or do not pose a risk to an in scope asset.
  • Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability).
  • Hard to exploit SSL/TLS protocol vulnerabilities, missing best practices in SSL/TLS configuration.
  • Known-vulnerable library (without evidence of exploitability).
  • Login/logout CSRF.
  • Low impact host header issues.
  • Missing best practices in Content Security Policy.
  • Missing email best practices (Invalid, incomplete, or missing SPF/DKIM/DMARC records, etc.).
  • Missing HttpOnly or Secure flags on cookies.
  • Missing http security headers which do not lead to a vulnerability.
  • Open ports which do not lead directly to a vulnerability.
  • Open redirect - unless an additional security impact can be demonstrated.
  • Password and account recovery policies, such as reset link expiration or password complexity.
  • Physical security of Eurofins facilities, employees, equipment, etc.
  • Rate limiting or brute-force issues on non-authentication endpoints.
  • Reports from automated tools or scans without a working Proof of Concept.
  • Software version disclosure / banner identification issues / descriptive error messages or headers (e.g. stack traces, application, or server errors).
  • Tabnabbing.
  • Testing third-party applications, websites, or services that integrate with or link to Eurofins properties.
  • Tests in a manner that would corrupt the operation of Eurofins solutions.
  • Vulnerabilities only affecting users of outdated or unpatched browsers and platforms.
  • Vulnerabilities which require a jailbroken device.

Rules

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

While testing

  • Submit your report in English.
  • Do not discuss or disclose any vulnerabilities (even resolved ones). Keep them in full confidentiality without prior explicit written consent from Eurofins.
  • Do not infringe any applicable intellectual property rights or trade secrets, laws, or regulations.
  • Do provide as much information as possible about the potential issue you have discovered with reproducible steps
  • Remove all Eurofins Confidential Information, including Personal Data you got from the analysis once the report is resolved.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • Do not act in a way that would compromise safety of Eurofins services and/or Eurofins operation.
  • Do not lock, disclose, destroy or compromise integrity of Eurofins and its customers and partners data

Not accepted

  • Missing http security headers which do not lead to a vulnerability.
  • Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability).
  • Login/logout CSRF.
  • Password and account recovery policies, such as reset link expiration or password complexity.
  • Clickjacking without an impact.
  • Content spoofing / reflection / injection (on 404 page, search result page etc.) unless executes code.
  • Known-vulnerable library (without evidence of exploitability).
  • Certain reports of spam.
  • Missing best practices in Content Security Policy.
  • Missing HttpOnly or Secure flags on cookies.
  • Missing email best practices (Invalid, incomplete, or missing SPF/DKIM/DMARC records, etc.).
  • Low impact host header issues.
  • Hard to exploit SSL/TLS protocol vulnerabilities, missing best practices in SSL/TLS configuration.
  • Rate limiting or brute-force issues on non-authentication endpoints.
  • 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.
  • Open ports which do not lead directly to a vulnerability.
  • Reports from automated tools or scans without a working Proof of Concept.
  • Exposed credentials that are either no longer valid, or do not pose a risk to an in scope asset.
  • Vulnerabilities only affecting users of outdated or unpatched browsers and platforms.
  • Email enumeration.
  • Cookie and logout policies.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Vulnerabilities which require a jailbroken device.

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