Skip to content

Emsisoft

Bug bounty on security.txt emsisoft.com

Accepting reports security.txt expired mentions bounty
Top reward
$500
Top severity paid
Not published
Assets in scope
1
Public CVEs
20
Last change
No changes yet

At a glance

What to know before you start testing.

Pays up to $500
top reward.
Report by email
[email protected]
Partial safe harbor
Some legal protection; read the terms.
Replies within 10 days
As the policy promises.
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.

Top reward
$500 we pay up to $500 USD per accepted security vulnerability
Response
Within 10 days it may take us up to 10 business days to review and respond
Safe harbor
Partial our bug bounty program will only reward researchers who follow responsible disclosure guidelines and never disclose any information about the vulnerability to the public or any entity other than Emsisoft before the issue has been fixed and the fix has been rolled out to our customers.
Hall of fame
Yes we also give credit to researchers in our release notes

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

Domains 1

  • emsisoft.com
Out of scope (2)
  • store.emsisoft.com
  • support.emsisoft.com

Rules

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

While testing

  • never disclose any information about the vulnerability to the public or any entity other than Emsisoft before the issue has been fixed and the fix has been rolled out to our customers.
  • We require a working proof-of-concept and won’t accept any automated reports or reports for theoretical issues.
  • Please include as much information as possible in your submission, but as a minimum we expect steps to reproduce the vulnerability and an explanation of why you consider it as such.
  • remember to mark it as private if you use any public hosting or streaming services like YouTube.

Not accepted

  • Non-detection of malware or protection bypasses, with the exception of bypasses that can’t be fixed with the addition of additional rules or signatures.
  • Issues that are non-exploitable but lead to crashes, information leaks, or stability issues.
  • Descriptive error messages (e.g. Stack traces, application or server errors).
  • HTTP 404 codes/pages or other HTTP non-200 codes/pages.
  • Banner disclosure on common/public services.
  • Disclosure of known public files or directories, (e.g. robots.txt, publicly accessible login forms).
  • Clickjacking and issues only exploitable through clickjacking.
  • Self-XSS and issues exploitable only through Self-XSS.
  • CSRF on forms that are available to the public without registration (e.g. the contact form).
  • Logout Cross-Site Request Forgery (logout CSRF).
  • Presence of application or web browser “autocomplete” or “save password”.
  • Issues that require physical access to the device to carry out the exploit.
  • Theoretical issues that lack practical severity.
  • Mail configuration issues related to DKIM, DMARC or SPF.
  • Missing security headers, SSL configuration issues, as well as non-secure elements being pulled into secure sites.
  • Vulnerabilities where a fix is not feasible.
  • Redirect issues, unless the redirect can be used to exfiltrate sensitive information (authentication tokens for example).
  • Non-amplified bruteforce attacks.
  • Attacks relying on social engineering or access to the user’s email account, unless access to said account was obtained through a vulnerability in our products.

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
CVESeverityPublished
CVE-2019-7651 High 7.5 8 Feb 2019
CVE-2012-1459 Medium 4.3 21 Mar 2012
CVE-2012-1461 Medium 4.3 21 Mar 2012
CVE-2012-1462 Medium 4.3 21 Mar 2012
CVE-2012-1448 Medium 4.3 21 Mar 2012
CVE-2012-1450 Medium 4.3 21 Mar 2012
CVE-2012-1451 Medium 4.3 21 Mar 2012
CVE-2012-1452 Medium 4.3 21 Mar 2012
CVE-2012-1453 Medium 4.3 21 Mar 2012
CVE-2012-1456 Medium 4.3 21 Mar 2012
CVE-2012-1457 Medium 4.3 21 Mar 2012
CVE-2012-1429 Medium 4.3 21 Mar 2012
CVE-2012-1432 Medium 4.3 21 Mar 2012
CVE-2012-1433 Medium 4.3 21 Mar 2012
CVE-2012-1434 Medium 4.3 21 Mar 2012
CVE-2012-1435 Medium 4.3 21 Mar 2012
CVE-2012-1436 Medium 4.3 21 Mar 2012
CVE-2012-1443 Medium 4.3 21 Mar 2012
CVE-2012-1423 Medium 4.3 21 Mar 2012
CVE-2012-1425 Medium 4.3 21 Mar 2012