CVE-2023-25826

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2023-05-03. NVD baseline CVSS 9.8; sources differ by 0.0.

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

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

Due to insufficient validation of parameters passed to the legacy HTTP query API, it is possible to inject crafted OS commands into multiple parameters and execute malicious code on the OpenTSDB host system. This exploit exists due to an incomplete fix that was made when this vulnerability was previously disclosed as CVE-2020-35476. Regex validation that was implemented to restrict allowed input to the query API does not work as intended, allowing crafted commands to bypass validation.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
85(Attend)
EG Risk 85/100SSVC: Attend

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%
Exploitation65% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
98.3%
KEV
Not listed

Published

May 3, 2023

Last Modified

February 13, 2025

Advisory Details (2)

Auto-updated Jun 21, 2026
Patch available. Sources: github_pr.
generic

New OpenTSDB Vulnerabilities Discovered by Black Duck CyRC | Black Duck Blog

https://www.synopsys.com/blogs/software-security/opentsdb/
github_pr Patch Available

Improved fix for #2261.

Patch available: OpenTSDB/opentsdb v2.5.0RC1 (PR #2275 merged 2023-04-11)

https://github.com/OpenTSDB/opentsdb/pull/2275

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
mavennet.opentsdb:opentsdb—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
net.opentsdb:opentsdb2.1.3 ... 2.4.1 (13 versions)——

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

Publicly available exploits

(1 reference)

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

  • Metasploitexploit/linux/http/opentsdb_key_cmd_injection✓ verified
    First seen Jul 1, 2023

    OpenTSDB 2.4.1 unauthenticated command injection

    Open source ↗

Frequently asked(5)

What is CVE-2023-25826?
CVE-2023-25826 is a critical vulnerability published on May 3, 2023. Due to insufficient validation of parameters passed to the legacy HTTP query API, it is possible to inject crafted OS commands into multiple parameters and execute malicious code on the OpenTSDB host system. This exploit exists due to an incomplete fix that was made when this vulnerability was…
When was CVE-2023-25826 disclosed?
CVE-2023-25826 was first published in the National Vulnerability Database on May 3, 2023, with the most recent update on February 13, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-25826 actively exploited?
CVE-2023-25826 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-25826?
CVE-2023-25826 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2023-25826?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-25826, 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-2023-25826

Explore →

Is Your Infrastructure Affected by CVE-2023-25826?

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

Start Free Scan →Browse All CVEs