datadog
Datadog's client library for Ruby
View on Github
Activity
- Latest release
- 3d ago
- Total releases
- 54
- Cadence
- ~14 days
- Last 12 months
- 25
Reach
- Downloads
- 36.8M
- Stars
- 417
Details
- License
- BSD-3-Clause OR Apache-2.0
- First release
- Mar 22, 2024
| Version | Released | |
|---|---|---|
2.47.0
minor
|
2.47.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.46.0
minor
|
2.46.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.45.0
minor
|
2.45.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.44.0
minor
|
2.44.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.43.0
minor
|
2.43.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.42.0
minor
|
2.42.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.41.0
minor
|
2.41.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.40.0
minor
|
2.40.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.39.0
minor
|
2.39.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.38.0
minor
|
2.38.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.37.0
minor
|
2.37.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.36.0
minor
|
2.36.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.35.0
minor
|
2.35.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.34.0
minor
|
2.34.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.33.0
minor
|
2.33.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.32.0
minor
|
2.32.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.31.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.31.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.30.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.30.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.29.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.29.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.28.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.28.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.27.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.27.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.26.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.26.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.25.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.25.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.24.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.24.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.23.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.23.0
minor
Dependencies (6)
Changelog
Compare changes
|
|
2.22.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.22.0
minor
Dependencies (5)
Changelog
Compare changes
|
|
2.21.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.21.0
minor
Dependencies (5)
Changelog
Compare changes
|
|
2.20.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.20.0
minor
Dependencies (5)
Changelog
Compare changes
|
|
2.19.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.19.0
minor
Dependencies (5)
Changelog
Compare changes
|
|
2.18.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.18.0
minor
Dependencies (5)
Changelog
Compare changes
|
|
2.17.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.17.0
minor
Dependencies (5)
Changelog
Compare changes
|
|
2.16.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.16.0
minor
Dependencies (5)
Changelog
Compare changes
|
|
2.15.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.15.0
minor
Dependencies (5)
Changelog
Compare changes
|
|
2.14.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.14.0
minor
Dependencies (5)
Changelog
Compare changes
|
|
2.13.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.13.0
minor
Dependencies (5)
Changelog
Compare changes
|
|
2.12.2
patch
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.12.2
patch
Dependencies (5)
Changelog
Compare changes
|
|
2.12.1
patch
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.12.1
patch
Dependencies (5)
Changelog
Compare changes
|
|
2.12.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.12.0
minor
Dependencies (5)
Changelog
Compare changes
|
|
2.11.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.11.0
minor
Dependencies (5)
Changelog
Compare changes
|
|
2.10.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.10.0
minor
Dependencies (5)
Changelog
Compare changes
|
|
2.9.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.9.0
minor
Dependencies (4)
Changelog
Compare changes
|
|
2.8.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.8.0
minor
Dependencies (4)
Changelog
Compare changes
|
|
2.7.1
patch
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.7.1
patch
Dependencies (4)
Changelog
Compare changes
|
|
2.7.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.7.0
minor
Dependencies (4)
Changelog
Compare changes
|
|
2.6.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.6.0
minor
Dependencies (4)
Changelog
Compare changes
|
|
2.5.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.5.0
minor
Dependencies (4)
Changelog
Compare changes
|
|
2.4.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.4.0
minor
Dependencies (4)
Changelog
Compare changes
|
|
2.3.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.3.0
minor
Dependencies (4)
Changelog
Compare changes
|
|
2.2.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.2.0
minor
Dependencies (4)
Changelog
Compare changes
|
|
2.1.0
minor
1 CVE
CVE-2026-50276
GHSA-p5f6-rccc-jv98
Jul 15, 2026
dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactDatadog 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. PatchesThis is resolved in version 2.32.0 and later of the WorkaroundsIf users cannot upgrade immediately:
ResourcesRelated upstream advisories: opentelemetry-go GHSA-mh2q-q3fh-2475 opentelemetry-dotnet GHSA-g94r-2vxg-569j Affected versions
2.0.0
2.0.0.beta1
2.0.0.beta2
2.0.0.rc1
2.1.0
2.10.0
2.11.0
2.12.0
2.12.1
2.12.2
2.13.0
2.14.0
+ 26 more Show less
2.15.0
2.16.0
2.17.0
2.18.0
2.19.0
2.2.0
2.20.0
2.21.0
2.22.0
2.23.0
2.24.0
2.25.0
2.26.0
2.27.0
2.28.0
2.29.0
2.3.0
2.30.0
2.31.0
2.4.0
2.5.0
2.6.0
2.7.0
2.7.1
2.8.0
2.9.0
Fixed in
2.32.0
References Updated Jul 15, 2026 · Source: OSV.dev |
2.1.0
minor
Dependencies (4)
Changelog
Compare changes
|