https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 14 Oct 2026 04:16:05 +0000 https://db.gcve.eu/vuln/ghsa-q7rr-3cgh-j5r3 <p><strong>Affected:</strong> npm: @opentelemetry/exporter-prometheus, npm: @opentelemetry/sdk-node, npm: @opentelemetry/auto-instrumentations-node</p> <p>## Summary</p> <p>A single malformed HTTP request crashes any Node.js process running the OpenTelemetry JS Prometheus exporter. The metrics endpoint (default `0.0.0.0:9464`) has no error handling around URL parsing, so a request with an invalid URI causes an uncaught `TypeError` that terminates the process.</p> <p>**You are affected by this vulnerability if either of the following apply to your application:**</p> <p>* you directly use `@opentelemetry/exporter-prometheus` in your code through its built-in server. * your `OTEL_METRICS_EXPORTER` environment variable includes `prometheus` **AND** * you use `@opentelemetry/sdk-node` * you use `@opentelemetry/auto-instrumentations-node` via `--require @opentelemetry/auto-instrumentations-node/register`/`--import @opentelemetry/auto-instrumentations-node/register`</p> <p>## Impact</p> <p>**Denial of service.** Any application using the OpenTelemetry Prometheus exporter’s built-in server can be crashed by a single unauthenticated network packet sent to the metrics port. No authentication, special privileges, or prior access is required.</p> <p>## Remediation</p> <p>### Update to the fixed version</p> <p>Update `@opentelemetry/exporter-prometheus` and `@opentelemetry/sdk-node` to version **0.217.0** or later. Update `@opentelemetry/auto-instrumentations-node` to version **0.75.0** or later.</p> <p>This release adds proper error handling around the URL constructor, returning an HTTP `400` response on parse failure rather than allowing the exception to propagate and crash the proces…</p> <p><strong>Affected:</strong> npm: @opentelemetry/exporter-prometheus, npm: @opentelemetry/sdk-node, npm: @opentelemetry/auto-instrumentations-node</p> <p>## Summary</p> <p>A single malformed HTTP request crashes any Node.js process running the OpenTelemetry JS Prometheus exporter. The metrics endpoint (default `0.0.0.0:9464`) has no error handling around URL parsing, so a request with an invalid URI causes an uncaught `TypeError` that terminates the process.</p> <p>**You are affected by this vulnerability if either of the following apply to your application:**</p> <p>* you directly use `@opentelemetry/exporter-prometheus` in your code through its built-in server. * your `OTEL_METRICS_EXPORTER` environment variable includes `prometheus` **AND** * you use `@opentelemetry/sdk-node` * you use `@opentelemetry/auto-instrumentations-node` via `--require @opentelemetry/auto-instrumentations-node/register`/`--import @opentelemetry/auto-instrumentations-node/register`</p> <p>## Impact</p> <p>**Denial of service.** Any application using the OpenTelemetry Prometheus exporter’s built-in server can be crashed by a single unauthenticated network packet sent to the metrics port. No authentication, special privileges, or prior access is required.</p> <p>## Remediation</p> <p>### Update to the fixed version</p> <p>Update `@opentelemetry/exporter-prometheus` and `@opentelemetry/sdk-node` to version **0.217.0** or later. Update `@opentelemetry/auto-instrumentations-node` to version **0.75.0** or later.</p> <p>This release adds proper error handling around the URL constructor, returning an HTTP `400` response on parse failure rather than allowing the exception to propagate and crash the proces…</p> https://db.gcve.eu/vuln/ghsa-q7rr-3cgh-j5r3