High [CVE-2026-59892] @opentelemetry/propagator-jaeger: OpenTelemetry JavaScript: Denial of Service via malformed HTTP header decoding
This high-severity Red Hat Linux advisory covers CVE-2026-59892 affecting Red Hat Developer Hub 1.10, Red Hat Developer Hub 1.9, Self-service automation portal 2.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Summary
OpenTelemetry JavaScript is the OpenTelemetry JavaScript client.
Prior to 2.9.0, @opentelemetry/propagator-jaeger decodes incoming uber-trace-id and uberctx-* HTTP header values with decodeURIComponent() without handling decode errors, allowing an unauthenticated remote attacker to send a malformed percent-encoded value that throws an uncaught URIError and terminates a Node.js process using JaegerPropagator as the active propagator.
This issue is fixed in version 2.9.0. Successful exploitation of this flaw can terminate a Node.js process, resulting in a Denial of Service (DoS).
This flaw affects the @opentelemetry/propagator-jaeger package used by container images that configure the Jaeger trace-context propagator. Red Hat CVSS score (7.5, Important) is consistent with upstream and NVD scoring.
Weakness: CWE-248. Affected Red Hat products: Red Hat Developer Hub 1.10; Red Hat Developer Hub 1.9; Self-service automation portal 2.
Red Hat lists OpenShift Serverless as not affected. Red Hat fixing advisory: RHSA-2026:49642, RHSA-2026:52768.
Is CVE-2026-59892 exploited?
No exploitation is reported in the sources VulniPulse tracks: CVE-2026-59892 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.
How do I fix CVE-2026-59892?
Upgrade to a fixed release named by Red Hat:
- 2.9.0
- rhdh/rhdh-hub-rhel9:1785411652
- rhdh/rhdh-hub-rhel9:1785972843
- RHSA-2026:49642
- RHSA-2026:52768
Confirm against the vendor advisory before you patch.
- < 2.9.0
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
- 2.9.0
- rhdh/rhdh-hub-rhel9:1785411652
- rhdh/rhdh-hub-rhel9:1785972843
- RHSA-2026:49642
- RHSA-2026:52768
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Mitigation checklist
- Administrators can mitigate this issue by not configuring JaegerPropagator as the active OpenTelemetry propagator (use W3C Trace Context or B3 propagation instead), or by deploying an ingress/proxy in front of the affected service that validates or strips uber-trace-id and uberctx-* headers before they reach the application. Upgrading to @opentelemetry/propagator-jaeger >= 2.9.0 resolves the issue upstream.
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Get an email when Red Hat publishes the next one.
See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
More Red Hat Linux advisories
- CVE-2026-119977Oct 31, 2026Arbitrary code execution via predictable upgrade staging paths
- CVE-2026-111497Oct 22, 2026Out-of-Bounds Write in Google Brotli Decoder
- CVE-2026-109619Oct 21, 2026fatal error handling retains stale request state leading to use-after-free
- CVE-2026-109618Oct 21, 2026OOM bailout during request parsing leads to memory corruption and RCE
- CVE-2026-97229Oct 13, 2026integer overflow issue in CI/CD regular expression compiler
- CVE-2026-64849Aug 17, 2026Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed
iPhone and Android apps · New on the App Store
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.