Skip to content
Web

CVE-2026-16286

9.8
Critical
EPSS 0.32%Patch availableAug 26, 2026

Unrestricted upload allows attackers to install web shells on TRtek repository servers.

common questions

Is CVE-2026-16286 being exploited?

Not confirmed. CVE-2026-16286 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.

How severe is CVE-2026-16286?

CVE-2026-16286 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-16286?

Yes. A fix has been recorded for CVE-2026-16286. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-16286 affect?

CVE-2026-16286 affects TRtek Software Repository Management (<2fb4acee), Web servers hosting the application. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-16286?

Upgrade to commit 2fb4acee or later; restrict/validate uploads and scan for web shells.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
TRtek Software Repository Management (<2fb4acee)Web servers hosting the application
impact

Attacker can upload a web shell for remote code execution, full server compromise and lateral movement.

action required

Immediate action required

affected versions
TRtek Technological Products Computer Software Hardware Industry and Trade Limited Company Software Repository Management
  • affected< 2fb4acee

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free