{"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-45684 exists.","fix":"Upgrade go.opentelemetry.io/obi to 0.9.0 or later.","what":"CVE-2026-45684 is a medium-severity memory corruption vulnerability in open-telemetry opentelemetry-ebpf-instrumentation, published on 2 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-45684 and fix it if it is affected.\n\nWhat it is: CVE-2026-45684 is a medium-severity memory corruption vulnerability in open-telemetry opentelemetry-ebpf-instrumentation, published on 2 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45684 exists.\n\nAffected packages and fixed versions:\n- go.opentelemetry.io/obi (Go): affected from 0.7.0; fixed in 0.9.0\n- go.opentelemetry.io/obi (Go): affected from 0.7.0; fixed in 0.9.0\n- go.opentelemetry.io/obi (Go): affected from 0.7.0; 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-45684/ (Markdown: https://insights.sbomify.com/CVE-2026-45684/index.md)","id":"CVE-2026-45684","markdown":"https://insights.sbomify.com/CVE-2026-45684/index.md","name":"CVE-2026-45684","record":{"aliases":["GHSA-vvmg-8mjr-g6q3","GO-2026-5677"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"OpenTelemetry eBPF instrumentation","requires_auth":"none","summary":"Attackers can trigger memory corruption via crafted writev calls when log injection is enabled, potentially leading to code execution or data modification.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"ebpf_instrumentation","vendor":"opentelemetry"}],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-126","name":"Buffer Over-read"}],"description":"OpenTelemetry eBPF Instrumentation provides eBPF instrumentation based on the OpenTelemetry standard. From version 0.7.0 to before version 0.9.0, OBI's log enricher mishandles writev buffers by reading only the first iovec entry but using the total iov_iter.count as the copy length. When log injection is enabled, a crafted multi-segment writev call can make OBI read and overwrite memory beyond the first segment. 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: Log enricher writev path can overread and overwrite user buffers","id":"CVE-2026-45684","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"OpenTelemetry eBPF Instrumentation: MongoDB parser panics on malformed wire messages","id":"CVE-2026-45685"},"packages":[{"ecosystem":"Go","fixed":["0.9.0"],"introduced":["0.7.0"],"last_affected":[],"package":"go.opentelemetry.io/obi","purl":null,"source":"GHSA-vvmg-8mjr-g6q3"},{"ecosystem":"Go","fixed":["0.9.0"],"introduced":["0.7.0"],"last_affected":[],"package":"go.opentelemetry.io/obi","purl":"pkg:golang/go.opentelemetry.io/obi","source":"GHSA-vvmg-8mjr-g6q3"},{"ecosystem":"Go","fixed":["0.9.0"],"introduced":["0.7.0"],"last_affected":[],"package":"go.opentelemetry.io/obi","purl":"pkg:golang/go.opentelemetry.io/obi","source":"GO-2026-5677"}],"prev":{"headline":"OpenTelemetry eBPF Instrumentation: Java TLS ioctl kprobe allows kernel memory disclosure","id":"CVE-2026-45683"},"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":6.5,"headline":"OpenTelemetry eBPF Instrumentation: Redis error text is exported in span status messages","id":"CVE-2026-45679","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-02","vendors":["open-telemetry"]},"summary":"Attackers can trigger memory corruption via crafted writev calls when log injection is enabled, potentially leading to code execution or data modification.","url":"https://insights.sbomify.com/CVE-2026-45684/"}