<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-17T11:21:11.225439+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-406508</id>
    <title>EUVD-2026-406508</title>
    <updated>2026-11-17T11:21:11.228587+00:00</updated>
    <content>EUVD-2026-406508</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-406508"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-rrfc-gjm9-cgrj</id>
    <title>GHSA-rrfc-gjm9-cgrj — OpenTelemetry-Go: Eager W3C baggage-property materialization causes bounded memory-allocation amplification</title>
    <updated>2026-11-17T11:21:11.228628+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: go.opentelemetry.io/otel/baggage, Go: go.opentelemetry.io/otel/propagation</p>
<p>## Summary</p>
<p>OpenTelemetry Go eagerly materializes W3C baggage metadata into property objects during parsing. Slice growth, serialization, and copying into the internal representation cause **bounded but disproportionate memory-allocation amplification** for a valid, densely populated header. In v1.46.0 and v1.47.0-rc.1, the 8,192-byte raw-input limit is checked before member parsing; this is not unlimited allocation or a bypass of that limit.</p>
<p>A valid 8,191-byte value containing one member and 4,094 properties causes approximately 778 KB of cumulative allocation per parse. A corrected measurement with forced garbage collection before and after parsing retains approximately 164 KB per result while it remains live. These are different metrics: approximately 95 times the input in allocation traffic versus approximately 20 times in incremental live heap in the measured environment.</p>
<p>The relevant security configuration is a service that enables Baggage propagation and extracts attacker-controlled inbound context before authentication or on a public route. Concurrent or sustained requests can increase allocation and GC pressure. The evidence establishes allocation amplification, but does not establish reliable OOM, process termination, or complete denial of service.</p>
<p>This is a **pre-existing, independent allocation-amplification path not addressed by GHSA-5wrp-cwcj-q835 / CVE-2026-41178**. It predates that advisory; it is not described as having been introduced by its fix.</p>
<p>## Aff…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-rrfc-gjm9-cgrj"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-128086</id>
    <title>msrc_CVE-2026-128086 — OpenTelemetry-Go: Eager W3C baggage-property materialization causes bounded memory-allocation amplification</title>
    <updated>2026-11-17T11:21:11.228704+00:00</updated>
    <content>msrc_CVE-2026-128086</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-128086"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-128086</id>
    <title>UBUNTU-CVE-2026-128086</title>
    <updated>2026-11-17T11:21:11.228726+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:22.04:LTS: golang-opentelemetry-otel, Ubuntu:24.04:LTS: golang-opentelemetry-otel, Ubuntu:26.10: golang-opentelemetry-otel, Ubuntu:26.04:LTS: golang-opentelemetry-otel</p>
<p>OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 1.0.0-RC1 until version 1.47.0, baggage.Parse and propagation.Baggage.Extract eagerly materialize every W3C baggage property through parseMember, grow property slices, serialize members, and copy properties into internal/baggage.Item. A valid densely populated baggage header can therefore cause allocation traffic and retained memory disproportionate to its bounded input size. Remote impact requires baggage extraction to be enabled, attacker-controlled input to reach it, and extraction to run before authentication or on a public route; the evidence establishes increased allocation and garbage-collection pressure but not reliable process termination. This issue is fixed in version 1.47.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-128086"/>
  </entry>
</feed>
