Skip to content
Applications

CVE-2016-20096

9.3
Critical
EPSS 0.67%Jul 22, 2026

Unauthenticated SQL injection in Linknat VOS login allows full DB access.

common questions

Is CVE-2016-20096 being exploited?

Not confirmed. CVE-2016-20096 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.67% probability of exploitation in the next 30 days.

How severe is CVE-2016-20096?

CVE-2016-20096 is rated Critical with a CVSS score of 9.3. 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-2016-20096?

Not known from our data. No patch reference has been recorded for CVE-2016-20096, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2016-20096 affect?

CVE-2016-20096 affects Linknat VOS3000 <= 2.1.2.0, Linknat VOS2009 <= 2.1.2.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2016-20096?

Apply vendor patch if available; block/limit login endpoint and isolate affected systems.

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

executive summary
technical analysis
affected
Linknat VOS3000 <= 2.1.2.0Linknat VOS2009 <= 2.1.2.0
impact

Unauthenticated SQL injection via POST 'name' lets attackers execute arbitrary SQL, extract plaintext credentials and DBA-level data.

action required

Immediate action required

affected versions
Kunshi Network Technology Co., Ltd. Linknat VOS2009
  • affected2.1.1.5
  • affected2.1.1.8
  • affected2.1.2.0
Kunshi Network Technology Co., Ltd. Linknat VOS3000
  • affected2.1.1.5
  • affected2.1.1.8
  • affected2.1.2.0

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