Vulnerability Reporting & Disclosure Policy

Effective as of March 1, 2026

TuxCare, Inc. is an authorized CVE Numbering Authority (CNA) registered with the CVE Program (cve.org). Our CNA scope covers vulnerabilities in products developed, maintained, and distributed by TuxCare, Inc., including TuxCare Endless Lifecycle Support (ELS) and TuxCare SecureChain for OSS.

As a CNA, TuxCare can assign CVE IDs directly for in-scope vulnerabilities and publish authoritative CVE Records on cve.org. This policy describes how to report vulnerabilities to us and what to expect from the disclosure process.

How to Report a Vulnerability

Send vulnerability reports to [email protected]. For sensitive disclosures, encrypt your message using our Security PGP key.

Please include:

  • Vulnerability type (e.g., RCE, privilege escalation, SQL injection, information disclosure)
  • Affected product, service, or component — and version if known
  • Step-by-step reproduction instructions
  • Supporting evidence (screenshots, logs, proof-of-concept code)
  • Your assessment of the potential impact

The Disclosure Process 

When you report a vulnerability to TuxCare, here is what will happen:

Step 1 — Acknowledgment

We will acknowledge receipt of your report within 3 business days.

Step 2 — Triage and CVE ID Assignment

Within 5 business days of acknowledgment, we will assess whether the issue is a valid vulnerability within our CNA scope.

  • If confirmed in scope, we assign a CVE ID within 24 hours of the triage decision and notify you of the CVE ID and our planned disclosure timeline. We also provide an initial severity assessment (CVSS score).
  • If the issue is out of our CNA scope, we will direct you to the appropriate CNA or refer you to cveform.mitre.org to avoid duplicate assignments.
  • If the report does not qualify as a vulnerability, we will explain our reasoning.

Step 3 — Remediation

We work to develop and verify a fix. Our standard embargo period is 90 days from the date of confirmed triage. We will provide progress updates as remediation proceeds. If additional time is needed due to complexity, we will notify you promptly and request a reasonable extension.

Step 4 — Coordinated Public Disclosure

Once a patch is ready and tested:

  1. We notify you of the planned publication date for the advisory.
  2. We publish a public security advisory at tuxcare.com/cve-tracker.
  3. Within 24 hours of the advisory going live, we publish the CVE Record on cve.org.
  4. The embargo lifts, and you are free to publish your own research.

Your Role as a Reporter

Coordinated disclosure requires a shared commitment. We ask that you:

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

If you publicly disclose before we have published a patch, we reserve the right to accelerate our advisory publication timeline without advance notice.

We will not initiate legal action against researchers who act in good faith in accordance with this policy.

Recognition

TuxCare does not operate a paid bug bounty program. With your permission, we credit researchers in the relevant security advisory and CVE Record, and we are glad to acknowledge good-faith contributions to the security of our products even where no CVE is warranted.

In-Scope Vulnerabilities

Products covered by TuxCare’s CNA scope (CVE IDs assigned directly)

TuxCare is the authoritative CNA for vulnerabilities in:

  • TuxCare Endless Lifecycle Support (ELS) — all supported operating systems and programming language versions
  • TuxCare SecureChain for OSS

For confirmed vulnerabilities in these products, TuxCare will assign a CVE ID within 24 hours of triage and publish the CVE Record on cve.org within 24 hours of the public advisory.

Additional products accepted (outside CNA scope)

We also accept vulnerability reports for TuxCare Live Patching software (KernelCare). Because Live Patching is not currently within our CNA scope, we will not assign CVE IDs for these reports directly — if a CVE ID is warranted, we will coordinate with the appropriate CNA and keep you informed. The same disclosure process and timelines apply.

Out-of-Scope Issues

The following are generally not accepted as valid vulnerabilities:

  • 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

TuxCare’s Commitments

 

Commitment  Timeline
Acknowledge your report Within 3 business days
Assign a CVE ID (if in scope) Within 24 hours of triage decision
Notify you of CVE ID and severity Same notification as CVE assignment
Provide remediation updates Throughout the embargo period
Publish the CVE Record on cve.org Within 24 hours of the public advisory
Credit you in the advisory and CVE record With your permission

 

Contact and PGP Key

Email: [email protected]

PGP key: https://keys.openpgp.org/search?q=security%40tuxcare.com

For general questions or non-security issues, see tuxcare.com/contact.