<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 09:40:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-32280 — Unexpected work during chain building in crypto/x509</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-32280</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go standard library crypto/x509, Red Hat Cryostat 4 on RHEL 9, Red Hat HawtIO HawtIO 4.4.0, Red Hat Ansible Automation Platform 2.5 for RHEL 8, Red Hat Ansible Automation Platform 2.5 for RHEL 9, Red Hat Ansible Automation Platform 2.6 for RHEL 10, Red Hat Ansible Automation Platform 2.6 for RHEL 9, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support, Red Hat Enterprise Linux 7 Extended Lifecycle Support and 132 more&lt;/p&gt;
&lt;p&gt;During chain building, the amount of work that is done is not correctly limited when a large number of intermediate certificates are passed in VerifyOptions.Intermediates, which can lead to a denial of service. This affects both direct users of crypto/x509 and users of crypto/tls.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go standard library crypto/x509, Red Hat Cryostat 4 on RHEL 9, Red Hat HawtIO HawtIO 4.4.0, Red Hat Ansible Automation Platform 2.5 for RHEL 8, Red Hat Ansible Automation Platform 2.5 for RHEL 9, Red Hat Ansible Automation Platform 2.6 for RHEL 10, Red Hat Ansible Automation Platform 2.6 for RHEL 9, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support, Red Hat Enterprise Linux 7 Extended Lifecycle Support and 132 more&lt;/p&gt;
&lt;p&gt;During chain building, the amount of work that is done is not correctly limited when a large number of intermediate certificates are passed in VerifyOptions.Intermediates, which can lead to a denial of service. This affects both direct users of crypto/x509 and users of crypto/tls.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-32280</guid>
    </item>
    <item>
      <title>GHSA-mh2q-q3fh-2475 — OpenTelemetry-Go: multi-value `baggage` header extraction causes excessive allocations (remote dos amplification)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mh2q-q3fh-2475</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: go.opentelemetry.io/otel&lt;/p&gt;
&lt;p&gt;multi-value `baggage:` header extraction parses each header field-value independently and aggregates members across values. this allows an attacker to amplify cpu and allocations by sending many `baggage:` header lines, even when each individual value is within the 8192-byte per-value parse limit.&lt;/p&gt;
&lt;p&gt;## severity&lt;/p&gt;
&lt;p&gt;HIGH (availability / remote request amplification)&lt;/p&gt;
&lt;p&gt;## relevant links&lt;/p&gt;
&lt;p&gt;- repository: https://github.com/open-telemetry/opentelemetry-go
- pinned callsite: https://github.com/open-telemetry/opentelemetry-go/blob/1ee4a4126dbdd1bc79e9fae072fa488beffac52a/propagation/baggage.go#L58&lt;/p&gt;
&lt;p&gt;## vulnerability details&lt;/p&gt;
&lt;p&gt;**pins:** open-telemetry/opentelemetry-go@1ee4a4126dbdd1bc79e9fae072fa488beffac52a
**as-of:** 2026-02-04
**policy:** direct (no program scope provided)&lt;/p&gt;
&lt;p&gt;**callsite:** propagation/baggage.go:58 (`extractMultiBaggage`)
**attacker control:** inbound HTTP request headers (many `baggage` field-values) → `propagation.HeaderCarrier.Values(&amp;#34;baggage&amp;#34;)` → repeated `baggage.Parse` + member aggregation&lt;/p&gt;
&lt;p&gt;### root cause&lt;/p&gt;
&lt;p&gt;`extractMultiBaggage` iterates over all `baggage` header field-values and parses each one independently, then appends members into a shared slice. the 8192-byte parsing cap applies per header value, but the multi-value path repeats that work once per header line (bounded only by the server/proxy header byte limit).&lt;/p&gt;
&lt;p&gt;### impact&lt;/p&gt;
&lt;p&gt;in a default `net/http` configuration (max header bytes 1mb), a single request with many `baggage:` header field-values can cause large per…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: go.opentelemetry.io/otel&lt;/p&gt;
&lt;p&gt;multi-value `baggage:` header extraction parses each header field-value independently and aggregates members across values. this allows an attacker to amplify cpu and allocations by sending many `baggage:` header lines, even when each individual value is within the 8192-byte per-value parse limit.&lt;/p&gt;
&lt;p&gt;## severity&lt;/p&gt;
&lt;p&gt;HIGH (availability / remote request amplification)&lt;/p&gt;
&lt;p&gt;## relevant links&lt;/p&gt;
&lt;p&gt;- repository: https://github.com/open-telemetry/opentelemetry-go
- pinned callsite: https://github.com/open-telemetry/opentelemetry-go/blob/1ee4a4126dbdd1bc79e9fae072fa488beffac52a/propagation/baggage.go#L58&lt;/p&gt;
&lt;p&gt;## vulnerability details&lt;/p&gt;
&lt;p&gt;**pins:** open-telemetry/opentelemetry-go@1ee4a4126dbdd1bc79e9fae072fa488beffac52a
**as-of:** 2026-02-04
**policy:** direct (no program scope provided)&lt;/p&gt;
&lt;p&gt;**callsite:** propagation/baggage.go:58 (`extractMultiBaggage`)
**attacker control:** inbound HTTP request headers (many `baggage` field-values) → `propagation.HeaderCarrier.Values(&amp;#34;baggage&amp;#34;)` → repeated `baggage.Parse` + member aggregation&lt;/p&gt;
&lt;p&gt;### root cause&lt;/p&gt;
&lt;p&gt;`extractMultiBaggage` iterates over all `baggage` header field-values and parses each one independently, then appends members into a shared slice. the 8192-byte parsing cap applies per header value, but the multi-value path repeats that work once per header line (bounded only by the server/proxy header byte limit).&lt;/p&gt;
&lt;p&gt;### impact&lt;/p&gt;
&lt;p&gt;in a default `net/http` configuration (max header bytes 1mb), a single request with many `baggage:` header field-values can cause large per…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mh2q-q3fh-2475</guid>
    </item>
  </channel>
</rss>
