Improper Handling of Exceptional Conditions Affecting @opentelemetry/exporter-prometheus package, versions <0.217.0
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JS-OPENTELEMETRYEXPORTERPROMETHEUS-16758050
- published19 May 2026
- disclosed11 May 2026
- creditUnknown
Introduced: 11 May 2026
NewCVE-2026-44902 (opens in a new tab)How to fix?
Upgrade @opentelemetry/exporter-prometheus to version 0.217.0 or higher.
Overview
@opentelemetry/exporter-prometheus is an OpenTelemetry Exporter Prometheus provides a metrics endpoint for Prometheus
Affected versions of this package are vulnerable to Improper Handling of Exceptional Conditions via the PrometheusExporter process. An attacker can cause the process to terminate unexpectedly by sending a single malformed HTTP request to the metrics endpoint, resulting in an uncaught exception and process crash.
Note:
This is only exploitable if the application uses the built-in Prometheus exporter server or is configured with the OTEL_METRICS_EXPORTER environment variable including prometheus in combination with either @opentelemetry/sdk-node or @opentelemetry/auto-instrumentations-node.
Workaround
This vulnerability can be mitigated by restricting access to the metrics endpoint using network policies, binding the server to localhost, or placing the endpoint behind a reverse proxy that filters incoming requests.