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

Relution GmbH

Vulnerability disclosure program on security.txt relution.io

Accepting reports security.txt
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
10
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 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 We do not currently operate a monetary bug bounty program.
Response
Within 5 days Upon receiving a report, we will acknowledge receipt within five business days and start to validate and triage the reported vulnerability.
Safe harbor
Partial However, this policy cannot and does not guarantee immunity from criminal prosecution.
Hall of fame
Yes Public acknowledgment on our Security Advisories page → (with consent)

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

Scope

10 assets you may test, 4 excluded.

Domains 3

  • hub.relution.io
  • live.relution.io
  • relution.io

Web 2

  • Relution Hub
  • The Relution website

APIs 1

  • https://live.relution.io/web-api/index.html

Wildcard domains 1

  • *.relution.io

Products and areas 3

  • Mobile applications published by Relution on official app stores
  • The Relution Docker containers published to Docker Hub
  • The Relution platform and its associated services hosted at domains operated by Relution
Out of scope (4)
  • Other systems, networks, or applications operated by our customers, partners, or third parties
  • Physical premises and facilities of Relution GmbH
  • Relution software operated by our customers, partners, or third parties
  • Third-party services integrated into our platform (e.g., payment processors, identity providers, analytics services)

Rules

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

While testing

  • Act in good faith with the sole purpose of identifying and reporting security vulnerabilities
  • Minimize harm : avoid actions that could impact system availability, data integrity, or other users
  • Stop upon discovery : once a vulnerability has been confirmed, cease further testing and report the findings
  • Protect data : do not access, copy, modify, or delete data belonging to other users
  • Maintain confidentiality : do not disclose vulnerability details to third parties until we have had reasonable opportunity to address the issue
  • Any form of social engineering, phishing, vishing, pretexting, or similar activities against Relution employees or users
  • Denial of service (DoS/DDoS) attacks or any testing intended to degrade service availability
  • Automated vulnerability scanning at volumes or frequencies that could impact system performance
  • Accessing, downloading, or otherwise exfiltrating customer data, personal data, or confidential business information
  • Public disclosure of vulnerabilities before coordinated disclosure has been agreed upon

Not accepted

  • Vulnerabilities requiring physical access to a user’s device
  • Vulnerabilities in third-party applications or services
  • Social engineering attacks
  • Denial of service vulnerabilities
  • Issues identified by automated scanners without demonstrated exploitability
  • Missing security headers without demonstrated impact
  • Clickjacking without demonstrated sensitive action
  • Self-XSS (user can only execute script in their own session)
  • CSRF on non-sensitive functionality
  • Information disclosure of non-sensitive data
  • Software version disclosure without associated vulnerability
  • Theoretical vulnerabilities without proof of concept
  • Issues already known to us or previously reported

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.