CVE-2016-20096

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-21. The CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's description, written by its CNA (VulnCheck), states the affected versions: "Linknat VOS3000 and VOS2009 through version 2.1.2.0 contain an unauthenticated SQL injection vulnerability that allows remote attackers to execute arbitrary SQL commands by manipulating the name parameter in a POST requ…" No release containing a fix is confirmed on record.

Linknat VOS3000 and VOS2009 through version 2.1.2.0 contain an unauthenticated SQL injection vulnerability that allows remote attackers to execute arbitrary SQL commands by manipulating the name parameter in a POST request to the login endpoint. Attackers can inject malicious SQL through the login form and retrieve injected query results from a subsequent session request, enabling extraction of plaintext credentials and other database content with DBA-level privileges.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 21, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Oct 15, 2026
No fix on record yet.
Web page

Linknat VOS3000/VOS2009 2.1.2.0 SQL Injection via login.jsp | Advisories | VulnCheck

https://www.vulncheck.com/advisories/linknat-vos3000-vos2009-sql-injection-via-login-jsp
Web page

VOS 系列软交换 | 昆石 linknat - 全球领先的 VoIP 解决方案供应商 | VOS5000 VosPower VOS3800 VOS3000 CKPBX IVR SBC

https://www.linknat.com/
Web page

某VoIP运营支撑系统存在通用型SQL注入&任意文件遍历漏洞(大量企业受影响) | WooYun-2015-145458 | WooYun.org

https://web.archive.org/web/20160601102456/http://www.wooyun.org/bugs/wooyun-2010-0145458

Vendor Advisories for CVE-2016-20096(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 62× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 404 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 305 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-20 01:17 UTCEG score recompute
  2. 2026-10-20 01:17 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-19 16:26 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  4. 2026-10-19 00:09 UTCEG score recompute
  5. 2026-10-19 00:09 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-18 16:26 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  7. 2026-10-18 10:52 UTCEG score recompute
  8. 2026-10-18 02:12 UTCEG score recompute
  9. 2026-10-18 02:11 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-17 16:26 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  11. 2026-10-17 04:13 UTCEG score recompute
  12. 2026-10-17 04:12 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-16 16:28 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  14. 2026-10-16 06:13 UTCEG score recompute
  15. 2026-10-16 06:12 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-15 16:26 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  17. 2026-10-15 04:49 UTCEG score recompute
  18. 2026-10-15 04:49 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-14 16:27 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  20. 2026-10-14 00:43 UTCEG score recompute
  21. 2026-10-14 00:42 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-13 16:27 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  23. 2026-10-12 20:46 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-12 20:45 UTCEG score recompute
  25. 2026-10-12 16:27 UTCEPSS rescoreEPSS 0.7% · 50th percentile
Show 74 more
  1. 2026-10-12 01:08 UTCEG score recompute
  2. 2026-10-11 13:40 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  3. 2026-10-10 19:54 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  4. 2026-10-09 20:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  5. 2026-10-08 16:35 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  6. 2026-10-07 23:40 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  7. 2026-10-06 15:11 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  8. 2026-10-05 17:38 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  9. 2026-10-04 23:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  10. 2026-10-04 14:48 UTCEG score recompute
  11. 2026-10-04 14:48 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-03 14:21 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  13. 2026-10-01 19:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  14. 2026-10-01 15:06 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-01 11:18 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-01 07:28 UTCEG score recompute
  17. 2026-10-01 07:28 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-09-30 14:58 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  19. 2026-09-30 09:12 UTCEG score recompute
  20. 2026-09-28 13:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  21. 2026-09-28 09:59 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-09-28 06:08 UTCEG score recompute
  23. 2026-09-28 06:08 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-09-27 13:40 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  25. 2026-09-26 15:53 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  26. 2026-09-24 15:01 UTCEG score recompute
  27. 2026-09-24 15:01 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-09-24 13:59 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  29. 2026-09-24 12:09 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-09-24 08:16 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-09-24 03:22 UTCEG score recompute
  32. 2026-09-24 03:22 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-09-23 13:41 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  34. 2026-09-23 09:13 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-09-23 05:24 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-09-23 01:25 UTCEG score recompute
  37. 2026-09-23 01:25 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-09-20 05:57 UTCEG score recompute
  39. 2026-09-20 05:57 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-09-19 15:35 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  41. 2026-09-19 00:20 UTCEG score recompute
  42. 2026-09-19 00:20 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-09-18 19:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  44. 2026-09-18 11:26 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-09-18 07:37 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-09-18 03:48 UTCEG score recompute
  47. 2026-09-18 03:48 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-09-17 19:21 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  49. 2026-09-17 09:52 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-09-17 05:05 UTCEG score recompute
  51. 2026-09-17 05:05 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-09-16 12:38 UTCEG score recompute
  53. 2026-09-16 12:38 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-09-15 03:05 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  55. 2026-09-14 10:19 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-09-14 06:17 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-09-14 02:28 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-09-13 22:39 UTCEG score recompute
  59. 2026-09-13 22:39 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-09-13 16:41 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  61. 2026-09-13 15:57 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-09-13 11:26 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-09-13 07:01 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-09-13 02:53 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-09-12 19:01 UTCEG score recompute
  66. 2026-09-12 19:01 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-09-12 14:55 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  68. 2026-09-12 13:36 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-09-12 09:47 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-09-12 05:47 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-09-12 01:56 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-09-11 22:07 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-09-11 18:17 UTCEG score recompute
  74. 2026-09-11 18:17 UTCGHSA enrichmentGHSA-36f2-4m9x-c736 · GitHub severity CRITICAL · GitHub CVSS 9.8

Frequently asked(5)

What is CVE-2016-20096?
CVE-2016-20096 is a critical-severity vulnerability; its CVE record was published on July 21, 2026. Linknat VOS3000 and VOS2009 through version 2.1.2.0 contain an unauthenticated SQL injection vulnerability that allows remote attackers to execute arbitrary SQL commands by manipulating the name parameter in a POST request to the login endpoint. Attackers can inject malicious SQL through the login…
When was CVE-2016-20096 made public?
CVE-2016-20096 was made public on July 21, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 21, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2016-20096 actively exploited?
CVE-2016-20096 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2016-20096?
CVE-2016-20096 has a CVSS base score of 9.8 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2016-20096?
No fix for CVE-2016-20096 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's description, written by its CNA (VulnCheck), states the affected versions: "Linknat VOS3000 and VOS2009 through version 2.1.2.0 contain an unauthenticated SQL injection vulnerability that allows remote attackers to execute arbitrary SQL commands by manipulating the name parameter in a POST requ…" No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2016-20096 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2016-20096

Explore →

Is Your Infrastructure Affected by CVE-2016-20096?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.