Skip to content

KNIME

Bug bounty on security.txt knime.com

Accepting reports security.txt
Top reward
Not published
Top severity paid
Not published
Assets in scope
2
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]
Replies within 1 day
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.

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

Pays cash
Yes Once we can confirm that the issue is real, we will pay a reward depending on its severity (according to the CVSS score).
Response
Within 1 days We do our best to acknowledge reception of a report within one business day.

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

Scope

2 assets you may test.

Domains 1

  • knime.com

Products and areas 1

  • KNIME software products and services

Rules

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

While testing

  • Please send one plain-text email for each vulnerability you are reporting.
  • We may ask you to resubmit your report if you send it as an image, movie, HTML, or PDF attachment when you could as easily describe it with plain text.
  • You do not need to encrypt submissions, and it takes us longer to respond to encrypted reports.
  • you should not contact these members individually about security issues

Not accepted

  • regular bug reports
  • other security-related queries
  • how to configure KNIME Software securely
  • whether a published vulnerability applies to specific versions of KNIME Software you are using
  • whether a published vulnerability applies to the configuration of the KNIME Software you are using
  • obtaining further information on a published vulnerability
  • the availability of patches and/or new releases to address a published vulnerability

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.