CVE-2026-45678

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% 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, secondary
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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

OpenTelemetry eBPF Instrumentation provides eBPF instrumentation based on the OpenTelemetry standard. Prior to version 0.9.0, the Postgres protocol parser assumes BIND message payloads contain a valid NUL-terminated portal name. A crafted empty or unterminated payload can make OBI slice beyond the end of the captured buffer and panic. This issue has been patched in version 0.9.0.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
26.2%
KEV
Not listed

Published

May 18, 2026

Last Modified

June 3, 2026

Advisory Details (2)

Auto-updated Jun 6, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
github Patch Available🟡 PoC Available

Postgres BIND parsing can panic on malformed payloads · Advisory · open-telemetry/opentelemetry-ebpf-instrumentation · GitHub

https://github.com/open-telemetry/opentelemetry-ebpf-instrumentation/security/advisories/GHSA-pgvv-q3wf-mm9m
github_release Patch Available

v0.9.0

Patch available: open-telemetry/opentelemetry-ebpf-instrumentation v0.9.0

https://github.com/open-telemetry/opentelemetry-ebpf-instrumentation/releases/tag/v0.9.0

Vendor Advisories for CVE-2026-45678(1)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
go.opentelemetry.io/obi—0.9.0—

Weakness Classification(2)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-45678?
CVE-2026-45678 is a high vulnerability published on May 18, 2026. OpenTelemetry eBPF Instrumentation provides eBPF instrumentation based on the OpenTelemetry standard. Prior to version 0.9.0, the Postgres protocol parser assumes BIND message payloads contain a valid NUL-terminated portal name. A crafted empty or unterminated payload can make OBI slice beyond the…
When was CVE-2026-45678 disclosed?
CVE-2026-45678 was first published in the National Vulnerability Database on May 18, 2026, with the most recent update on June 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45678 actively exploited?
CVE-2026-45678 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 26.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45678?
CVE-2026-45678 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-45678?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45678, 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-2026-45678

Explore →

Is Your Infrastructure Affected by CVE-2026-45678?

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

Start Free Scan →Browse All CVEs