llamaCVEVulnerability Intelligence
/
Advisory · GitHub · Go · go.opentelemetry.io/otel/schema/v1.1

GHSA-995V-FVRW-C78M

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

Parche disponible
Descargar PNG JSON
CVSS
—
low
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche2 versionesPrimer parche a -1 d de la divulgación
Exposición175 dDesde la divulgación, 28 may 2026, 12:19 p. m.
Detección172 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Modificada
Explotación
Remediación
Parche v0.0.17
Monitoreo
Detectada
27 may 26
28 may 26
15 jul 26
17 nov 26
19 nov 26
27 may 26
10 jul 26
23 ago 26
6 oct 26
19 nov 26
FechaFaseEventoDetalle
Remediación Parche v0.0.17 go.opentelemetry.io/otel/schema · -1 d desde divulgación
Divulgación Publicada GHSA-995V-FVRW-C78M divulgada
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen
Descripción del advisory
Texto original · GitHub · en inglés
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:

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:

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

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.

Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.

Versiones

Rangos afectados

Afectada Corregida Última
go.opentelemetry.io/otel/schema/v1.1 · go.opentelemetry.io/otel/schema/v1.0 · go.opentelemetry.io/otel/schema< 0.0.17
0.0.17
v0.0.19
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
gogo.opentelemetry.io/otel/schema
Corregida v0.0.17 -1 d v0.0.19 no afectada
Versiones corregidas0.0.17v0.0.17
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2026-45287
Otrahttps://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-995v-fvrw-c78m
Otrahttps://github.com/open-telemetry/opentelemetry-go/commit/e72a235518cb773137efd80336a179028bc34684
Otrahttps://github.com/open-telemetry/opentelemetry-go/commit/f12d198f161b61735d65705248715aa97021ba8d
Otrahttps://github.com/open-telemetry/opentelemetry-go

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.