{"answers":{"affected":"3 open source packages ship an affected version, including go.opentelemetry.io/obi. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45679 exists.","fix":"Upgrade go.opentelemetry.io/obi to 0.9.0 or later.","what":"CVE-2026-45679 is a medium-severity vulnerability in open-telemetry opentelemetry-ebpf-instrumentation, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-45679 and fix it if it is affected.\n\nWhat it is: CVE-2026-45679 is a medium-severity vulnerability in open-telemetry opentelemetry-ebpf-instrumentation, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45679 exists.\n\nAffected packages and fixed versions:\n- go.opentelemetry.io/obi (Go): affected all versions; fixed in 0.9.0\n- go.opentelemetry.io/obi (Go): affected all versions; fixed in 0.9.0\n- go.opentelemetry.io/obi (Go): affected all versions; fixed in 0.9.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-45679/ (Markdown: https://insights.sbomify.com/CVE-2026-45679/index.md)","id":"CVE-2026-45679","markdown":"https://insights.sbomify.com/CVE-2026-45679/index.md","name":"CVE-2026-45679","record":{"aliases":["GHSA-8rrq-wcg8-cv5q","GO-2026-5265"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenTelemetry eBPF instrumentation","requires_auth":"none","summary":"Attackers can exfiltrate sensitive Redis error data, including tokens and PII, into telemetry backends via OpenTelemetry eBPF instrumentation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"ebpf_instrumentation","vendor":"opentelemetry"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"},{"id":"CWE-117","name":"Improper Output Neutralization for Logs"}],"description":"OpenTelemetry eBPF Instrumentation provides eBPF instrumentation based on the OpenTelemetry standard. Prior to version 0.9.0, OBI exports raw Redis error text as the span status message. Because Redis error replies can contain attacker-controlled or sensitive values, this behavior can exfiltrate tokens, PII, or other confidential input into telemetry backends and inject untrusted text into downstream analysis systems. This issue has been patched in version 0.9.0.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"OpenTelemetry eBPF Instrumentation: Redis error text is exported in span status messages","id":"CVE-2026-45679","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"OpenTelemetry eBPF Instrumentation: Unbounded BPF internal metrics replay can exhaust CPU","id":"CVE-2026-45680"},"packages":[{"ecosystem":"Go","fixed":["0.9.0"],"introduced":["0"],"last_affected":[],"package":"go.opentelemetry.io/obi","purl":null,"source":"GHSA-8rrq-wcg8-cv5q"},{"ecosystem":"Go","fixed":["0.9.0"],"introduced":["0"],"last_affected":[],"package":"go.opentelemetry.io/obi","purl":"pkg:golang/go.opentelemetry.io/obi","source":"GHSA-8rrq-wcg8-cv5q"},{"ecosystem":"Go","fixed":["0.9.0"],"introduced":["0"],"last_affected":[],"package":"go.opentelemetry.io/obi","purl":"pkg:golang/go.opentelemetry.io/obi","source":"GO-2026-5265"}],"prev":{"headline":"OpenTelemetry eBPF Instrumentation: Postgres BIND parsing can panic on malformed payloads","id":"CVE-2026-45678"},"products":["opentelemetry-ebpf-instrumentation"],"published":"2026-06-02","related":[{"cvss_score":7.5,"headline":"OpenTelemetry eBPF Instrumentation: Postgres BIND parsing can panic on malformed payloads","id":"CVE-2026-45678","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":7.5,"headline":"OpenTelemetry eBPF Instrumentation: MongoDB parser panics on malformed wire messages","id":"CVE-2026-45685","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":7.5,"headline":"OpenTelemetry eBPF Instrumentation: Memcached payload length overflow can crash OBI","id":"CVE-2026-45686","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":5.9,"headline":"OpenTelemetry eBPF Instrumentation: Unbounded BPF internal metrics replay can exhaust CPU","id":"CVE-2026-45680","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":5.9,"headline":"OpenTelemetry eBPF Instrumentation: CPU-mismatch fallback uses 256-byte buffer with 8KB size","id":"CVE-2026-45681","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":5.5,"headline":"OpenTelemetry eBPF Instrumentation: Unsafe fastelf parsing allows malformed ELF to crash agent","id":"CVE-2026-45676","kev_date_added":null,"published":"2026-06-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-02","vendors":["open-telemetry"]},"summary":"Attackers can exfiltrate sensitive Redis error data, including tokens and PII, into telemetry backends via OpenTelemetry eBPF instrumentation.","url":"https://insights.sbomify.com/CVE-2026-45679/"}