Most recent entries from all

CLEANSTART-2026-GR75196 — Security fix for CVE-2026-50272 applied in: langfuse-worker 3.194.1-r1

2026-10-03T17:17:13.433592+00:00

Affected: CleanStart: langfuse-worker

Security vulnerability affects the langfuse-worker package. This issue is resolved in later releases. See references for vulnerability details.

EUVD-2026-339088

2026-10-03T17:17:13.433650+00:00

EUVD-2026-339088

fkie_cve-2026-50272

2026-10-03T17:17:13.433668+00:00

dd-trace is the Datadog APM client for Node.js. Prior to 5.100.0, W3C baggage propagation in packages/dd-trace/src/baggage.js and packages/dd-trace/src/opentracing/propagation/text_map.js parsed incoming baggage HTTP headers without enforcing DD_TRACE_BAGGAGE_MAX_ITEMS or DD_TRACE_BAGGAGE_MAX_BYTES on extraction. A remote, unauthenticated attacker can send a request whose baggage header contains an arbitrarily large number of comma-separated key-value pairs, or a single very large value, causing unbounded CPU and memory consumption and enabling a remote denial of service against any HTTP service with baggage propagation enabled. This issue is fixed in version 5.100.0.

GHSA-wxqq-gcq8-c443 — dd-trace-js: Improper parsing of W3C baggage headers may lead to DoS

2026-10-03T17:17:13.433695+00:00

Affected: npm: dd-trace

### Impact Datadog tracing libraries that implement W3C baggage propagation parse incoming baggage HTTP headers without enforcing item-count or byte-size limits on the extract path. The DD_TRACE_BAGGAGE_MAX_ITEMS (default 64) and DD_TRACE_BAGGAGE_MAX_BYTES (default 8192) limits were applied only to baggage injection, not extraction. A remote, unauthenticated attacker can send a request whose baggage header contains an arbitrarily large number of comma-separated key-value pairs (or a single very large value). The tracer allocates a hash-map entry for each pair on every request, causing unbounded CPU and memory consumption and enabling a remote Denial of Service against any HTTP service that has the baggage propagation style enabled. The baggage propagation style is enabled by default in most affected tracers, so any internet-facing service that has been instrumented with an affected tracer version is exposed unless the propagation style has been explicitly narrowed.

### Patches This is resolved in version 5.100.0 and later of the `dd-trace-js` library.

### Workarounds If users cannot upgrade immediately: 1. Disable `baggage` extraction by removing `baggage` from `DD_TRACE_PROPAGATION_STYLE` (or `DD_TRACE_PROPAGATION_STYLE_EXTRACT` if set independently). 2. Cap the maximum HTTP request header size at an upstream proxy or web server (for example, Apache `LimitRequestFieldSize`, Nginx `large_client_header_buffers`, Envoy `max_request_headers_kb`).

### Resources Related upstr…