Skip to content

Ecosia GmbH

Vulnerability disclosure program on security.txt ecosia.org

Accepting reports Full safe harbor security.txt
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
5
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.
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 3 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 Note: Ecosia does not operate a Bug-Bounty program and we don't offer monetary rewards .
Response
Within 3 days Acknowledgement: Reports acknowledged within 72 hours .
Safe harbor
Full Authorized concerning any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy.

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

Scope

5 assets you may test, 6 excluded.

Domains 2

  • blog.ecosia.org
  • ecosia.org

APIs 1

  • Ecosia API Endpoints

iOS apps 1

  • com.ecosia.ios

Wildcard domains 1

  • *.ecosia.org
Out of scope (6)
  • Assets or other equipment not owned by parties participating in this policy.
  • Denial of Service (DoS) attacks, automated scanning, or resource exhaustion techniques.
  • Internal development and staging environments (e.g., staging.ecosia.org , dev.ecosia.org ).
  • Physical security concerns such as attacks on Ecosia offices or employee workstations.
  • Social engineering attacks, including phishing campaigns targeting Ecosia employees.
  • Third-party applications, integrations, or services not owned or controlled by Ecosia.

Rules

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

While testing

  • Report discovered vulnerabilities promptly.
  • Avoid actions that compromise privacy, disrupt systems, destroy data, or degrade user experience.
  • Communicate vulnerability details only through official channels.
  • Test only in-scope systems and avoid out-of-scope areas.
  • If a vulnerability exposes data, access only the minimum required, stop testing immediately upon encountering sensitive information (e.g. PII, PHI, credit card data), and report it.
  • Use only test accounts you own or have permission to access.
  • Never engage in extortion.

Not accepted

  • Lack enough detail to reproduce the issue
  • Are based on speculation or unverifiable claims
  • Contain only bulk scanner output without analysis
  • Describe known, accepted, or already addressed issues
  • Fall outside the program’s scope

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.