Vulnerabilities in pkg:golang/go.opentelemetry.io/otel/schema/v1.0

PACKAGE
Advisory Identifier: GHSA-995v-fvrw-c78m
Advisory Summary

CVE-2026-45287 is a LOW opentelemetry-go's schema parsefile leaks file vulnerability (CWE-772: Missing Release of Resource after Effective Lifetime) affecting Go.opentelemetry.io/otel/schema/v1.1 libraries in the Go ecosystem. The issue involves opentelemetry-go's schema parsefile leaks file descriptors on each parse. Remediation is available by upgrading affected packages to version 0.0.17.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/go.opentelemetry.io/otel/schema/v1.0

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/go.opentelemetry.io/otel/schema/v1.0. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-995v-fvrw-c78m CVE-2026-45287 LOW opentelemetry-go's Schema ParseFile leaks file descriptors on each parse

CVE-2026-45287 at a Glance

CVE Identifier CVE-2026-45287
GHSA Identifier GHSA-995v-fvrw-c78m
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-772: Missing Release of Resource after Effective Lifetime
Affected Product Go.opentelemetry.io/otel/schema/v1.1
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-45287

To remediate this vulnerability, upgrade all affected Go.opentelemetry.io/otel/schema/v1.1 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

go.opentelemetry.io/otel/schema/v1.1 fixed: 0.0.17
Upgrade go.opentelemetry.io/otel/schema/v1.1 to 0.0.17
go.opentelemetry.io/otel/schema/v1.0 fixed: 0.0.17
Upgrade go.opentelemetry.io/otel/schema/v1.0 to 0.0.17
go.opentelemetry.io/otel/schema fixed: 0.0.17
Upgrade go.opentelemetry.io/otel/schema to 0.0.17
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for go.opentelemetry.io/otel/schema/v1.1

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-45287, inspect your project dependencies for Go.opentelemetry.io/otel/schema/v1.1:

inspect dependencies for go.opentelemetry.io/otel/schema/v1.1

Analyze the terminal output to locate any version of Go.opentelemetry.io/otel/schema/v1.1 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.17), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-772: Missing Release of Resource after Effective Lifetime, where the product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed. In Go.opentelemetry.io/otel/schema/v1.1, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary `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. The severity is low because exploitation depends on a consuming application exposing repeated schema parsing to an attacker-controlled path. Introduced in commit: e72a235 ### Details In `schema/v1.0/parser.go:41-47`, `ParseFile` opens the requested schema path with `os.Open` and then returns `Parse(file)` without a `defer file.Close()` or other close path: ```go file, err := os.Open(schemaFilePath) if err != nil { return nil, err } return Parse(file) ``` The validation evidence also identifies `schema/v1.0/parser.go:50-73`: `Parse` accepts an `io.Reader`, decodes from it, and does not close it. Ownership of the opened file is therefore not transferred to `Parse`, leaving the descriptor open until the Go runtime eventually finalizes the file object. With repeated `ParseFile` calls, descriptors can accumulate until the process receives `EMFILE` / "too many open files". ### PoC [validation-artifact.zip](https://github.com/user-attachments/files/27494463/validation-artifact.zip) The local artifact `validation-artifact.zip` contains: - `leak_poc.go`: PoC source that repeatedly calls `schema.ParseFile("schema/v1.0/testdata/valid-example.yaml")` and prints `/proc/self/fd` counts. - `LEAK_POC_README.txt`: reproduction notes. - `leak_poc_run.log`: captured attempted run; the local offline environment failed before execution because Go module download from `proxy.golang.org` was forbidden. Reproduce from the root of a checkout of `pellared/opentelemetry-go` at commit `e72a235` with Go module dependencies already available: ```sh /bin/sh -c 'ulimit -n 256; GOGC=off go run leak_poc.go' ``` Configuration: - File descriptor soft limit: `256` - Garbage collection: disabled with `GOGC=off` so leaked descriptors are not reclaimed during the loop - Schema file: `schema/v1.0/testdata/valid-example.yaml` Expected output is increasing descriptor counts followed by an `EMFILE` failure, for example: ```text iter 0 fds 7 iter 50 fds 57 iter 100 fds 107 ... panic: iteration 248: open schema/v1.0/testdata/valid-example.yaml: too many open files ``` The exact initial descriptor count and failing iteration can vary by OS and process state. ### Impact This is a file descriptor resource leak leading to availability loss. Applications that call `schema.ParseFile` repeatedly, especially through a runtime reload or request-controlled path, can exhaust their process file descriptor table and fail subsequent file, socket, or other descriptor operations. Impact is limited to denial of service of the consuming process; the evidence does not show confidentiality or integrity impact.

CVE-2026-45287 Affected Go.opentelemetry.io/otel/schema/v1.1 Versions

3 component(s)
Fixed Versions:
0.0.17
Product / Package Ecosystem Affected Versions Fixed Version
go.opentelemetry.io/otel/schema/v1.1
Go
< 0.0.17
0.0.17
go.opentelemetry.io/otel/schema/v1.0
Go
< 0.0.17
0.0.17
go.opentelemetry.io/otel/schema
Go
< 0.0.17
0.0.17

References

Frequently Asked Questions

What is CVE-2026-45287?
CVE-2026-45287 is a security vulnerability in Go.opentelemetry.io/otel/schema/v1.1 involving opentelemetry-go's Schema ParseFile leaks file descriptors on each parse under CWE-772: Missing Release of Resource after Effective Lifetime.
Which Go.opentelemetry.io/otel/schema/v1.1 versions are affected?
Affected versions include releases prior to 0.0.17 across affected packages: go.opentelemetry.io/otel/schema/v1.1, go.opentelemetry.io/otel/schema/v1.0, go.opentelemetry.io/otel/schema.
What version fixes CVE-2026-45287?
Upgrading to 0.0.17 (or the latest patched release for your respective branch) resolves the vulnerability.
Is go.opentelemetry.io/otel/schema/v1.1 affected?
Yes, go.opentelemetry.io/otel/schema/v1.1 is affected in releases prior to 0.0.17. Upgrade your dependency to 0.0.17 or later.
Is go.opentelemetry.io/otel/schema/v1.0 affected?
Yes, go.opentelemetry.io/otel/schema/v1.0 is affected in releases prior to 0.0.17. Upgrade your dependency to 0.0.17 or later.
What CWE is associated with CVE-2026-45287?
CVE-2026-45287 is classified under CWE-772: Missing Release of Resource after Effective Lifetime (The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.).
How can I check Go dependencies for CVE-2026-45287?
Run the dependency tree command: 'inspect dependencies for go.opentelemetry.io/otel/schema/v1.1'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-995v-fvrw-c78m",
  "modified" : "2026-07-15T21:49:11Z",
  "published" : "2026-05-28T17:19:10Z",
  "aliases" : [ "CVE-2026-45287" ],
  "summary" : "opentelemetry-go's Schema ParseFile leaks file descriptors on each parse",
  "details" : "### Summary\n\n`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. The severity is low because exploitation depends on a consuming application exposing repeated schema parsing to an attacker-controlled path.\n\nIntroduced in commit: e72a235\n\n### Details\n\nIn `schema/v1.0/parser.go:41-47`, `ParseFile` opens the requested schema path with `os.Open` and then returns `Parse(file)` without a `defer file.Close()` or other close path:\n\n```go\nfile, err := os.Open(schemaFilePath)\nif err != nil {\n\treturn nil, err\n}\nreturn Parse(file)\n```\n\nThe validation evidence also identifies `schema/v1.0/parser.go:50-73`: `Parse` accepts an `io.Reader`, decodes from it, and does not close it. Ownership of the opened file is therefore not transferred to `Parse`, leaving the descriptor open until the Go runtime eventually finalizes the file object. With repeated `ParseFile` calls, descriptors can accumulate until the process receives `EMFILE` / \"too many open files\".\n\n### PoC\n\n[validation-artifact.zip](https://github.com/user-attachments/files/27494463/validation-artifact.zip)\n\nThe local artifact `validation-artifact.zip` contains:\n\n- `leak_poc.go`: PoC source that repeatedly calls `schema.ParseFile(\"schema/v1.0/testdata/valid-example.yaml\")` and prints `/proc/self/fd` counts.\n- `LEAK_POC_README.txt`: reproduction notes.\n- `leak_poc_run.log`: captured attempted run; the local offline environment failed before execution because Go module download from `proxy.golang.org` was forbidden.\n\nReproduce from the root of a checkout of `pellared/opentelemetry-go` at commit `e72a235` with Go module dependencies already available:\n\n```sh\n/bin/sh -c 'ulimit -n 256; GOGC=off go run leak_poc.go'\n```\n\nConfiguration:\n\n- File descriptor soft limit: `256`\n- Garbage collection: disabled with `GOGC=off` so leaked descriptors are not reclaimed during the loop\n- Schema file: `schema/v1.0/testdata/valid-example.yaml`\n\nExpected output is increasing descriptor counts followed by an `EMFILE` failure, for example:\n\n```text\niter 0 fds 7\niter 50 fds 57\niter 100 fds 107\n...\npanic: iteration 248: open schema/v1.0/testdata/valid-example.yaml: too many open files\n```\n\nThe exact initial descriptor count and failing iteration can vary by OS and process state.\n\n### Impact\n\nThis is a file descriptor resource leak leading to availability loss. Applications that call `schema.ParseFile` repeatedly, especially through a runtime reload or request-controlled path, can exhaust their process file descriptor table and fail subsequent file, socket, or other descriptor operations. Impact is limited to denial of service of the consuming process; the evidence does not show confidentiality or integrity impact.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "go.opentelemetry.io/otel/schema/v1.1"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.0.17"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.0.16"
    }
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "go.opentelemetry.io/otel/schema/v1.0"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.0.17"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.0.16"
    }
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "go.opentelemetry.io/otel/schema"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.0.17"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-995v-fvrw-c78m"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-45287"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-go/commit/e72a235518cb773137efd80336a179028bc34684"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-go/commit/f12d198f161b61735d65705248715aa97021ba8d"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/open-telemetry/opentelemetry-go"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-772", "CWE-775" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-28T17:19:10Z",
    "nvd_published_at" : "2026-06-04T16:16:38Z"
  }
}