CVE-2021-36711

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 15.5%, top 4% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 15%CVSS: 9.8Exploit: NoneExposed: 0

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

WebInterface in OctoBot before 0.4.4 allows remote code execution because Tentacles upload is mishandled.

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
96.5%
KEV
Not listed

Published

July 16, 2022

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Jun 12, 2026
No patch confirmed yet.
generic

OctoBot/CHANGELOG.md at master · Drakkar-Software/OctoBot · GitHub

https://github.com/Drakkar-Software/OctoBot/blob/master/CHANGELOG.md
generic

Automated trading strategies for crypto investors - OctoBot

https://www.octobot.online/
generic

Packet Storm

https://packetstormsecurity.com/files/167721/Sashimi-Evil-OctoBot-Tentacle.html

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
octobot0.2.4b1 ... 0.4.3 (55 versions)0.4.4—

Weakness Classification(1)

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

Data Freshness Timeline

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

Publicly available exploits

(1 reference)

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

  • Exploit-DBEDB-50979
    First seen Jul 21, 2022

    OctoBot WebInterface 0.4.3 - Remote Code Execution (RCE)

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2021-36711?
CVE-2021-36711 is a critical vulnerability published on July 16, 2022. WebInterface in OctoBot before 0.4.4 allows remote code execution because Tentacles upload is mishandled.
When was CVE-2021-36711 disclosed?
CVE-2021-36711 was first published in the National Vulnerability Database on July 16, 2022, 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-2021-36711 actively exploited?
CVE-2021-36711 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2021-36711?
CVE-2021-36711 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2021-36711?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-36711, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-36711

Explore →

Is Your Infrastructure Affected by CVE-2021-36711?

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

Start Free Scan →Browse All CVEs