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

TuxCare, Inc.

Vulnerability disclosure program on security.txt tuxcare.com

Accepting reports Full safe harbor security.txt
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
5
Public CVEs
0
Last change

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report by email
[email protected]
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 TuxCare does not operate a paid bug bounty program.
Response
Within 3 days We will acknowledge receipt of your report within 3 business days.
Safe harbor
Full We will not initiate legal action against researchers who act in good faith in accordance with this policy.
Hall of fame
No With your permission, we credit researchers in the relevant security advisory and CVE Record

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

Domains 2

  • kernelcare.com
  • tuxcare.com

Products and areas 3

  • TuxCare Endless Lifecycle Support (ELS)
  • TuxCare Live Patching software (KernelCare)
  • TuxCare SecureChain for OSS
Out of scope (7)
  • Attacks requiring physical access or a privileged network position (MITM) without demonstrated impact
  • Clickjacking on pages without sensitive actions
  • CSRF on unauthenticated endpoints
  • Denial-of-service attacks
  • Missing security headers without a working proof of concept
  • Social engineering of TuxCare staff
  • Software version or configuration disclosure

Rules

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

While testing

  • Hold disclosure until TuxCare has published its advisory and notified you that the embargo has lifted, or until 90 days have elapsed from your initial report — whichever comes first.
  • Coordinate on timing if you plan to publish independent research, so we can align the advisory publication date.
  • Minimize impact during your research: avoid destroying data, do not disrupt production systems beyond what is needed to confirm the vulnerability, and do not access data belonging to other users.
  • Use exploits only to confirm the vulnerability — do not leverage access for any other purpose.

Not accepted

  • Clickjacking on pages without sensitive actions
  • CSRF on unauthenticated endpoints
  • Attacks requiring physical access or a privileged network position (MITM) without demonstrated impact
  • Missing security headers without a working proof of concept
  • Denial-of-service attacks
  • Software version or configuration disclosure
  • Social engineering of TuxCare staff

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.

  1. Scope +

    Added to scope: kernelcare.com

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.