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

Elisa

Bug bounty on security.txt elisa.fi

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

The policy page has no reward table. Here is what it says, in its own words.

Pays cash
Yes We reward vulnerabilities only through and according to the policy and scope of our Bug Bounty program.
Safe harbor
Partial We only allow active testing in accordance with the rules defined in the Bug Bounty Program, and for the services defined in the program.

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.

Domains 3

  • elisa.com
  • elisa.ee
  • elisa.fi

Rules

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

While testing

  • We only allow active testing in accordance with the rules defined in the Bug Bounty Program, and for the services defined in the program.
  • Please report any vulnerability or suspected vulnerability you encountered as soon as possible and without undue delay.
  • Avoid violating people's privacy, disturbing our services, destroying or altering information and / or damaging our customer experience.
  • Communicate vulnerability information only through official communication channels.
  • Keep any information regarding detected vulnerabilities confidential.
  • Limit the amount of information you access to the minimum required to prove the vulnerability (Proof-of-Concept, PoC). Stop testing if you encounter sensitive information.
  • If a user account is required to demonstrate the vulnerability, use only accounts that you own.
  • Do not attempt to perform denial-of-service attacks or social engineering attacks (e.g. phishing).

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.