open-telemetry opentelemetry-go up to 0.0.16 release of resource

Summaryinfo

A vulnerability marked as problematic has been reported in open-telemetry opentelemetry-go up to 0.0.16. Affected by this vulnerability is an unknown functionality. Performing a manipulation results in release of resource. This vulnerability is cataloged as CVE-2026-45287. The attack must be initiated from a local position. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in open-telemetry opentelemetry-go up to 0.0.16. This affects an unknown code. The manipulation with an unknown input leads to a release of resource vulnerability. CWE is classifying the issue as CWE-772. The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed. This is going to have an impact on availability. The summary by CVE is:

OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to version 0.0.17, `go.opentelemetry.io/otel/schema/v1.0` and `go.opentelemetry.io/otel/schema/v1.1` leaks one file descriptor on each successful `ParseFile` call. `ParseFile` opens the schema file and passes it to `Parse` without closing it; repeated parsing in a long-running process can exhaust the process file descriptor limit and cause denial of service. Exploitation depends on a consuming application exposing repeated schema parsing to an attacker-controlled path. Version 0.0.17 contains a patch for the issue.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-45287 since 05/11/2026. The exploitability is told to be easy. Attacking locally is a requirement. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 318809 (Linux Distros Unpatched Vulnerability : CVE-2026-45287), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 0.0.17 eliminates this vulnerability. Applying the patch e72a235518cb773137efd80336a179028bc34684 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (318809). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• open-telemetry

Name

• opentelemetry-go

Version

• 0.0.1
• 0.0.2
• 0.0.3
• 0.0.4
• 0.0.5
• 0.0.6
• 0.0.7
• 0.0.8
• 0.0.9
• 0.0.10
• 0.0.11
• 0.0.12
• 0.0.13
• 0.0.14
• 0.0.15
• 0.0.16

License

• open-source

Website

• Product: https://github.com/open-telemetry/opentelemetry-go/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion