CVE-2020-11710

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-24. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 33%CVSS: 9.8Exploit: Elevated riskExposed: 0

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

An issue was discovered in docker-kong (for Kong) through 2.0.3. The admin API port may be accessible on interfaces other than 127.0.0.1. NOTE: The vendor argue that this CVE is not a vulnerability because it has an inaccurate bug scope and patch links. “1) Inaccurate Bug Scope - The issue scope was on Kong's docker-compose template, and not Kong's docker image itself. In reality, this issue is not associated with any version of the Kong gateway. As such, the description stating ‘An issue was discovered in docker-kong (for Kong) through 2.0.3.’ is incorrect. This issue only occurs if a user decided to spin up Kong via docker-compose without following the security documentation. The docker-compose template is meant for users to quickly get started with Kong, and is meant for development purposes only. 2) Incorrect Patch Links - The CVE currently points to a documentation improvement as a “Patch” link: https://github.com/Kong/docs.konghq.com/commit/d693827c32144943a2f45abc017c1321b33ff611.This link actually points to an improvement Kong Inc made for fool-proofing. However, instructions for how to protect the admin API were already well-documented here: https://docs.konghq.com/2.0.x/secure-admin-api/#network-layer-access-restrictions , which was first published back in 2017 (as shown in this commit: https://github.com/Kong/docs.konghq.com/commit/e99cf875d875dd84fdb751079ac37882c9972949) Lastly, the hyperlink to https://github.com/Kong/kong (an unrelated Github Repo to this issue) on the Hyperlink list does not include any meaningful information on this topic.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
65(Track*)
EG Risk 65/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
33%
EPSS %ILE
98%
KEV
Not listed

Published

April 12, 2020

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Aug 16, 2026
Patch available. Sources: github_commit.
generic

GitHub - Kong/kong: 🦍 The API and AI Gateway · GitHub

https://github.com/Kong/kong
github_commit

commit e99cf875d875 (Kong/docs.konghq.com)

Fix landed in Kong/docs.konghq.com commit e99cf875d875 — awaiting tagged release

https://github.com/Kong/docs.konghq.com/commit/e99cf875d875dd84fdb751079ac37882c9972949
github_commit

commit d693827c3214 (Kong/docs.konghq.com)

Fix landed in Kong/docs.konghq.com commit d693827c3214 — awaiting tagged release

https://github.com/Kong/docs.konghq.com/commit/d693827c32144943a2f45abc017c1321b33ff611
github_commit Patch Available

commit dfa095cadf7e (Kong/docker-kong)

Patch available: Kong/docker-kong 2.5.1 (contains commit dfa095cadf7e)

https://github.com/Kong/docker-kong/commit/dfa095cadf7e8309155be51982d8720daf32e31c

Data Freshness Timeline

(refreshed 8× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-21 00:45 UTCOSV refresh
  2. 2026-08-20 22:51 UTCEPSS rescore
  3. 2026-08-19 17:00 UTCEPSS rescore
  4. 2026-08-18 13:44 UTCEPSS rescore
  5. 2026-08-17 13:43 UTCEPSS rescore
  6. 2026-08-16 14:52 UTCEPSS rescore
  7. 2026-08-16 02:11 UTCEPSS rescore
  8. 2026-08-15 01:26 UTCEPSS rescore
  9. 2026-08-13 21:57 UTCEPSS rescore
  10. 2026-08-12 13:47 UTCEPSS rescore
  11. 2026-08-08 16:33 UTCEPSS rescore
  12. 2026-08-07 16:23 UTCEPSS rescore
  13. 2026-08-06 13:43 UTCEPSS rescore
  14. 2026-08-05 19:14 UTCEPSS rescore
  15. 2026-08-05 16:11 UTCOSV refresh
  16. 2026-08-04 15:06 UTCEPSS rescore
  17. 2026-08-03 10:32 UTCEPSS rescore
  18. 2026-08-01 04:12 UTCEPSS rescore
  19. 2026-07-30 16:24 UTCEPSS rescore
  20. 2026-07-30 01:27 UTCEPSS rescore
  21. 2026-07-28 15:32 UTCEPSS rescore
  22. 2026-07-26 14:51 UTCEPSS rescore
  23. 2026-07-25 14:14 UTCEPSS rescore
  24. 2026-07-24 14:14 UTCEPSS rescore
  25. 2026-07-23 14:15 UTCEPSS rescore
Show 63 more
  1. 2026-07-23 14:15 UTCEPSS rescore
  2. 2026-07-23 01:48 UTCEG score recompute
  3. 2026-07-22 22:33 UTCEG score recompute
  4. 2026-07-22 14:05 UTCEPSS rescore
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-19 14:55 UTCOSV refresh
  7. 2026-07-19 02:26 UTCEPSS rescore
  8. 2026-07-19 02:26 UTCEPSS rescore
  9. 2026-07-18 10:02 UTCEPSS rescore
  10. 2026-07-16 16:59 UTCEPSS rescore
  11. 2026-07-16 16:59 UTCEPSS rescore
  12. 2026-07-15 16:55 UTCEPSS rescore
  13. 2026-07-13 06:10 UTCEPSS rescore
  14. 2026-07-13 06:10 UTCEPSS rescore
  15. 2026-07-12 05:44 UTCEPSS rescore
  16. 2026-07-11 08:24 UTCEPSS rescore
  17. 2026-07-09 19:06 UTCEPSS rescore
  18. 2026-07-08 15:11 UTCEPSS rescore
  19. 2026-07-06 16:25 UTCEPSS rescore
  20. 2026-07-06 16:25 UTCEPSS rescore
  21. 2026-07-06 02:20 UTCEPSS rescore
  22. 2026-07-04 06:28 UTCEPSS rescore
  23. 2026-07-02 02:17 UTCOSV refresh
  24. 2026-07-01 15:03 UTCEPSS rescore
  25. 2026-07-01 15:03 UTCEPSS rescore
  26. 2026-06-28 04:54 UTCEPSS rescore
  27. 2026-06-28 04:54 UTCEPSS rescore
  28. 2026-06-27 03:06 UTCEPSS rescore
  29. 2026-06-25 13:47 UTCEPSS rescore
  30. 2026-06-25 13:47 UTCEPSS rescore
  31. 2026-06-24 14:03 UTCEPSS rescore
  32. 2026-06-24 14:03 UTCEPSS rescore
  33. 2026-06-23 21:31 UTCEPSS rescore
  34. 2026-06-23 21:31 UTCEPSS rescore
  35. 2026-06-21 01:57 UTCEPSS rescore
  36. 2026-06-21 01:57 UTCEPSS rescore
  37. 2026-06-18 17:50 UTCEPSS rescore
  38. 2026-06-18 17:50 UTCEPSS rescore
  39. 2026-06-17 17:50 UTCEPSS rescore
  40. 2026-06-17 17:50 UTCEPSS rescore
  41. 2026-06-16 17:50 UTCEPSS rescore
  42. 2026-06-16 17:50 UTCEPSS rescore
  43. 2026-06-15 17:46 UTCEPSS rescore
  44. 2026-06-14 05:13 UTCOSV refresh
  45. 2026-06-13 22:58 UTCEPSS rescore
  46. 2026-06-13 22:58 UTCEPSS rescore
  47. 2026-06-08 14:15 UTCEPSS rescore
  48. 2026-06-08 14:15 UTCEPSS rescore
  49. 2026-06-06 13:45 UTCEPSS rescore
  50. 2026-06-06 13:45 UTCEPSS rescore
  51. 2026-06-06 13:45 UTCEPSS rescore
  52. 2026-06-05 22:45 UTCEPSS rescore
  53. 2026-06-05 22:45 UTCEPSS rescore
  54. 2026-06-05 06:08 UTCEPSS rescore
  55. 2026-06-04 13:10 UTCEPSS rescore
  56. 2026-06-04 13:10 UTCEPSS rescore
  57. 2026-05-31 00:15 UTCEPSS rescore
  58. 2026-05-31 00:14 UTCEPSS rescore
  59. 2026-05-27 05:17 UTCEG score recompute
  60. 2026-05-27 05:17 UTCGHSA enrichment
  61. 2026-05-26 07:17 UTCEPSS rescore
  62. 2026-05-26 07:17 UTCEPSS rescore
  63. 2026-05-25 22:46 UTCOSV refresh

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2020/CVE-2020-11710.yaml
    First seen Jan 1, 2020

    Kong Admin <=2.03 - Admin API Access

    Open source ↗

Frequently asked(5)

What is CVE-2020-11710?
CVE-2020-11710 is a critical vulnerability published on April 12, 2020. An issue was discovered in docker-kong (for Kong) through 2.0.3. The admin API port may be accessible on interfaces other than 127.0.0.1. NOTE: The vendor argue that this CVE is not a vulnerability because it has an inaccurate bug scope and patch links. “1) Inaccurate Bug Scope - The issue scope…
When was CVE-2020-11710 disclosed?
CVE-2020-11710 was first published in the National Vulnerability Database on April 12, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-11710 actively exploited?
CVE-2020-11710 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33% probability of exploitation in the next 30 days, which ranks it in the top 1.8% of all scored CVEs.
What is the CVSS score of CVE-2020-11710?
CVE-2020-11710 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2020-11710?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-11710, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-11710

Explore →

Is Your Infrastructure Affected by CVE-2020-11710?

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

Start Free Scan →Browse All CVEs