opentelemetry-go's Schema ParseFile leaks file descriptors on each parse

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.1 · 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 · score source

EPSS

• CVE-2026-45287: 0.17% estimated exploitation activity in the next 30 days; percentile 6.07 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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: 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…

Published by the source

28 May 2026, 17:19 UTC

Last modified by the source

15 Jul 2026, 21:49 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-995v-fvrw-c78m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-45287

Advisory: opentelemetry-go's Schema ParseFile leaks file descriptors on each parse
IDs: CVE-2026-45287, GHSA-995v-fvrw-c78m
Record: https://patchnext.com/advisories/cve-2026-45287 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: go.opentelemetry.io/otel/schema 0.0.17; go.opentelemetry.io/otel/schema/v1.0 0.0.17; go.opentelemetry.io/otel/schema/v1.1 0.0.17. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go go.opentelemetry.io/otel/schema: affected < 0.0.17; fixed in 0.0.17
- Go go.opentelemetry.io/otel/schema/v1.0: affected <= 0.0.16; fixed in 0.0.17
- Go go.opentelemetry.io/otel/schema/v1.1: affected <= 0.0.16; fixed in 0.0.17

## Suggested inspection (read-only)
- Go go.opentelemetry.io/otel/schema: check the installed version with your package manager.
- Go go.opentelemetry.io/otel/schema/v1.0: check the installed version with your package manager.
- Go go.opentelemetry.io/otel/schema/v1.1: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on go.opentelemetry.io/otel/schema, go.opentelemetry.io/otel/schema/v1.0, go.opentelemetry.io/otel/schema/v1.1.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-995v-fvrw-c78m (GitHub-reviewed advisory GHSA-995v-fvrw-c78m lists affected ranges: Go go.opentelemetry.io/otel/schema/v1.1 >=0 =0 =0 <0.0.17)

Commands are suggestions: review each one before running it.