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

Tenable

Vulnerability disclosure program on HackerOne tenable.com

Accepting reports Full safe harbor
Go to program Website
Top reward
No cash rewards
Top severity paid
Critical
Assets in scope
15
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 on HackerOne
Submit through the program page.
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 5 days
As the policy promises.
No public write-ups
Keep findings private.

Rewards

What HackerOne lists as the payout for each severity.

This program does not pay cash rewards.

Response
Within 5 days Time to first response/acknowledgment (from report submit) - 5 business days
Safe harbor
Full Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

15 assets you may test, 16 excluded.

Desktop and binaries 2

  • Tenable Enclave Security Critical No bounty
  • Tenable Sensor Proxy Critical No bounty

Products and areas 13

  • Nessus Critical No bounty
  • Nessus Agent Critical No bounty
  • Nessus Network Monitor High No bounty
  • Tenable Attack Surface Management Critical No bounty
  • Tenable Cloud Security Critical No bounty
  • Tenable Core Critical No bounty
  • Tenable Identity Exposure Critical No bounty
  • Tenable Lumin Critical No bounty
  • Tenable One Exposure Management Platform Critical No bounty
  • Tenable OT Security Critical No bounty
  • Tenable Security Center Critical No bounty
  • Tenable Vulnerability Management Critical No bounty
  • Tenable Web Application Scanning Critical No bounty
Out of scope (16)
  • Terrascan
  • careers.tenable.com
  • cloud.tenable.com
  • community.tenable.com
  • de.tenable.com
  • developers.tenable.com
  • docs.tenable.com
  • fr.tenable.com
  • go.tenable.com
  • http://events.tenable.com
  • login.tenable.com
  • partners.tenable.com
  • static.tenable.com
  • suggestions.tenable.com
  • university.tenable.com
  • www.tenable.com

Rules

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

While testing

  • Submit one vulnerability per report
  • Social engineering of any type (e.g. phishing, vishing, smishing) is strictly prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
  • Please do not discuss any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.

Not accepted

  • Clickjacking or lack of Framing protection in headers
  • Unauthenticated/logout/login CSRF
  • Previously known vulnerable libraries without a new working Proof of Concept
  • Missing best practices in SSL/TLS and Header configuration.
  • Any activity that could lead to the disruption of our services (i.e., DoS, DDoS, etc).
  • Recently disclosed zero day vulnerabilities
  • Headers which disclose versioning information
  • Issues related to email spoofing
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Tabnabbing
  • Physical or social engineering attempts (this includes phishing attacks against Tenable employees)
  • Missing Cookie Flags
  • Self XSS or similar vulnerabilities
  • Bugs requiring exceedingly unlikely user interaction

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 1 hour 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.

Original policy

Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Introduction

Tenable supports responsible disclosure of security vulnerabilities, and we are committed to working with researchers to fully understand and resolve them. Tenable believes in responding quickly to reports, maintaining communication with researchers, and providing a solution in short order.

Response Targets

Tenable will make a best effort to meet the following response targets for hackers participating in our program:

  • Time to first response/acknowledgment (from report submit) - 5 business days
  • Time to triage (from report submit) - 10 business days
  • Time to resolution - depends on severity and complexity

The team will keep you informed about our progress throughout the process.

Disclosure Policy

  • Please do not discuss any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
  • Follow HackerOne's disclosure guidelines.

Program Rules

  • Submit one vulnerability per report
  • Include a description of the issue explaining the vulnerability, including the impact to the user(s) or system. This should clearly describe how the issue crosses privilege boundaries. The affected product or resource (e.g., Tenable.io, Nessus, Tenable.sc, web site), the software version, and the platform you are using (e.g., Windows 10, Debian Linux).
  • A proof-of-concept or functional exploit that demonstrates the issue. If a proof-of-concept is not available, please include any relevant logs generated from your testing.
  • Any caveats or conditions required to exploit the issue. Indicate if there are any non-default system settings, custom configurations, required user interaction, or anything else that would limit the attack.
  • Social engineering of any type (e.g. phishing, vishing, smishing) is strictly prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.

Out of scope vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

  • Clickjacking or lack of Framing protection in headers
  • Unauthenticated/logout/login CSRF
  • Previously known vulnerable libraries without a new working Proof of Concept
  • Missing best practices in SSL/TLS and Header configuration.
  • Any activity that could lead to the disruption of our services (i.e., DoS, DDoS, etc).
  • Recently disclosed zero day vulnerabilities
  • Headers which disclose versioning information
  • Issues related to email spoofing
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Tabnabbing
  • Physical or social engineering attempts (this includes phishing attacks against Tenable employees)
  • Missing Cookie Flags
  • Self XSS or similar vulnerabilities
  • Bugs requiring exceedingly unlikely user interaction

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep Tenable and our users safe!