CVE-2026-45678 | OpenTelemetry eBPF Instrumentation: Postgres BIND parsing can panic on malformed payloads

Exp

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.

Published: 2026-06-02 Last update: 2026-06-03 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-45678 is rated Exploit Available (51.6/100): CVSS High severity, with low exploitation likelihood (EPSS 0.06%). Core evidence: 1 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2026-45678

EDB-ID Source Kind Published Link
nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2026-45678

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-03 0.06%

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-45678

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9 3.6 [email protected]

Weakness enumeration for CVE-2026-45678

GitHub Security Advisory for CVE-2026-45678

GHSA-pgvv-q3wf-mm9m · Severity: high · Ecosystem: go — OpenTelemetry eBPF Instrumentation: Postgres BIND parsing can panic on malformed payloads

OS Trackers for CVE-2026-45678

vendor priority summary link
suse high https://www.suse.com/security/cve/CVE-2026-45678/

Affected software / configurations for CVE-2026-45678

Vendor Product Version Raw CPE
opentelemetry ebpf_instrumentation < 0.9.0 cpe:2.3:a:opentelemetry:ebpf_instrumentation:*:*:*:*:*:go:*:*

References for CVE-2026-45678

cvelogic Threat Intelligence