OpenTelemetry eBPF Instrumentation: Postgres BIND parsing can panic on malformed payloads
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-45678
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 5 Nov 2026, 05:55 UTC · Revision 1
Source evidence
OpenTelemetry eBPF Instrumentation: Postgres BIND parsing can panic on malformed payloads
core-osv · Original sourcePublished 2 Jun 2026, 15:24 UTC
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.
osv:CVE-2026-45678
Complete source record
{
"id": "6b1c00ada59aa7f0747ac41cb1c22c6c278dc3dc4b3fa67c3e34684ea44baa4b",
"url": "https://osv.dev/vulnerability/CVE-2026-45678",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "OpenTelemetry eBPF Instrumentation: Postgres BIND parsing can panic on malformed payloads",
"summary": "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.",
"evidence": "osv:CVE-2026-45678",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-45678",
"aliases": [
"CVE-2026-45678",
"GHSA-pgvv-q3wf-mm9m",
"GO-2026-5539"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/open-telemetry/opentelemetry-ebpf-instrumentation",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "e92b0c2dd4d88b90d28b7b706eacbac2fabd2623"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "0.9.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "e92b0c2dd4d88b90d28b7b706eacbac2fabd2623"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v0.9.0"
},
{
"cpe": "cpe:2.3:a:opentelemetry:ebpf_instrumentation:*:*:*:*:*:go:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "0.9.0"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"v0.8.0",
"v0.7.1",
"v0.7.0",
"v0.6.0",
"v0.5.0",
"v0.4.1",
"v0.4.0",
"v0.3.0",
"v0.2.0",
"v0.1.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-45678.json"
}
}
],
"modified": "2026-10-28T02:30:42.952873764Z",
"provider": "osv",
"references": [
"https://github.com/open-telemetry/opentelemetry-ebpf-instrumentation/releases/tag/v0.9.0",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/45xxx/CVE-2026-45678.json",
"https://github.com/open-telemetry/opentelemetry-ebpf-instrumentation/security/advisories/GHSA-pgvv-q3wf-mm9m",
"https://nvd.nist.gov/vuln/detail/CVE-2026-45678"
],
"provider_metadata": {
"cwe_ids": [
"CWE-20",
"CWE-754"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/45xxx/CVE-2026-45678.json"
}
},
"related_cves": [
{
"value": "CVE-2026-45678",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 510863,
"published_at": "2026-06-02T15:24:12.34+00:00"
}