<?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>Fri, 02 Oct 2026 16:54:17 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: CLEANSTART-2026-EP15881 — Security fixes in cert-manager-webhook-pdns-fips 2.3.0-r0</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-ep15881</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: cert-manager-webhook-pdns-fips&lt;/p&gt;
&lt;p&gt;Package cert-manager-webhook-pdns-fips version 2.3.0-r0 fixes 17 vulnerabilities: CVE-2022-1996, CVE-2023-45142, CVE-2023-25151, CVE-2022-21698, CVE-2022-30636...&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: cert-manager-webhook-pdns-fips&lt;/p&gt;
&lt;p&gt;Package cert-manager-webhook-pdns-fips version 2.3.0-r0 fixes 17 vulnerabilities: CVE-2022-1996, CVE-2023-45142, CVE-2023-25151, CVE-2022-21698, CVE-2022-30636...&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-ep15881</guid>
    </item>
    <item>
      <title>EUVD-2026-221599</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-221599</link>
      <description>EUVD-2026-221599</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-221599</guid>
    </item>
    <item>
      <title>fkie_cve-2023-25151</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-25151</link>
      <description>&lt;p&gt;opentelemetry-go-contrib is a collection of extensions for OpenTelemetry-Go. The v0.38.0 release of `go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp` uses the `httpconv.ServerRequest` function to annotate metric measurements for the `http.server.request_content_length`, `http.server.response_content_length`, and `http.server.duration` instruments. The `ServerRequest` function sets the `http.target` attribute value to be the whole request URI (including the query string)[^1]. The metric instruments do not &amp;#34;forget&amp;#34; previous measurement attributes when `cumulative` temporality is used, this means the cardinality of the measurements allocated is directly correlated with the unique URIs handled. If the query string is constantly random, this will result in a constant increase in memory allocation that can be used in a denial-of-service attack. This issue has been addressed in version 0.39.0. Users are advised to upgrade. There are no known workarounds for this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;opentelemetry-go-contrib is a collection of extensions for OpenTelemetry-Go. The v0.38.0 release of `go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp` uses the `httpconv.ServerRequest` function to annotate metric measurements for the `http.server.request_content_length`, `http.server.response_content_length`, and `http.server.duration` instruments. The `ServerRequest` function sets the `http.target` attribute value to be the whole request URI (including the query string)[^1]. The metric instruments do not &amp;#34;forget&amp;#34; previous measurement attributes when `cumulative` temporality is used, this means the cardinality of the measurements allocated is directly correlated with the unique URIs handled. If the query string is constantly random, this will result in a constant increase in memory allocation that can be used in a denial-of-service attack. This issue has been addressed in version 0.39.0. Users are advised to upgrade. There are no known workarounds for this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-25151</guid>
    </item>
    <item>
      <title>GHSA-5r5m-65gx-7vrh — otelhttp and otelbeego have DoS vulnerability for high cardinality metrics</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5r5m-65gx-7vrh</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp, Go: go.opentelemetry.io/contrib/instrumentation/github.com/astaxie/beego/otelbeego&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The [v0.38.0](https://github.com/open-telemetry/opentelemetry-go-contrib/releases/tag/v1.13.0) release of [`go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp`](https://github.com/open-telemetry/opentelemetry-go-contrib/blob/463c2e7cd69d25f40b0a595b05394eeb26c68ae2/instrumentation/net/http/otelhttp/handler.go#L218) uses the [`httpconv.ServerRequest`](https://github.com/open-telemetry/opentelemetry-go/blob/v1.12.0/semconv/internal/v2/http.go#L159) function to annotate metric measurements for the `http.server.request_content_length`, `http.server.response_content_length`, and `http.server.duration` instruments.&lt;/p&gt;
&lt;p&gt;The `ServerRequest` function sets the `http.target` attribute value to be the whole request URI (including the query string)[^1]. The metric instruments do not &amp;#34;forget&amp;#34; previous measurement attributes when `cumulative` temporality is used, this means the cardinality of the measurements allocated is directly correlated with the unique URIs handled. If the query string is constantly random, this will result in a constant increase in memory allocation that can be used in a denial-of-service attack.&lt;/p&gt;
&lt;p&gt;Pseudo-attack:
```
for infinite loop {
  r := generate_random_string()
  do_http_request(&amp;#34;/some/path?random=&amp;#34;+r)
}
```&lt;/p&gt;
&lt;p&gt;### Patches
- `go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp` - v0.39.0
- `go.opentelemetry.io/contrib/instrumentation/github.com/astaxie/beego/otelbeego` - v0.39.0&lt;/p&gt;
&lt;p&gt;[^1]: https://github.com/open-telemetry/opentelemetry-…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp, Go: go.opentelemetry.io/contrib/instrumentation/github.com/astaxie/beego/otelbeego&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The [v0.38.0](https://github.com/open-telemetry/opentelemetry-go-contrib/releases/tag/v1.13.0) release of [`go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp`](https://github.com/open-telemetry/opentelemetry-go-contrib/blob/463c2e7cd69d25f40b0a595b05394eeb26c68ae2/instrumentation/net/http/otelhttp/handler.go#L218) uses the [`httpconv.ServerRequest`](https://github.com/open-telemetry/opentelemetry-go/blob/v1.12.0/semconv/internal/v2/http.go#L159) function to annotate metric measurements for the `http.server.request_content_length`, `http.server.response_content_length`, and `http.server.duration` instruments.&lt;/p&gt;
&lt;p&gt;The `ServerRequest` function sets the `http.target` attribute value to be the whole request URI (including the query string)[^1]. The metric instruments do not &amp;#34;forget&amp;#34; previous measurement attributes when `cumulative` temporality is used, this means the cardinality of the measurements allocated is directly correlated with the unique URIs handled. If the query string is constantly random, this will result in a constant increase in memory allocation that can be used in a denial-of-service attack.&lt;/p&gt;
&lt;p&gt;Pseudo-attack:
```
for infinite loop {
  r := generate_random_string()
  do_http_request(&amp;#34;/some/path?random=&amp;#34;+r)
}
```&lt;/p&gt;
&lt;p&gt;### Patches
- `go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp` - v0.39.0
- `go.opentelemetry.io/contrib/instrumentation/github.com/astaxie/beego/otelbeego` - v0.39.0&lt;/p&gt;
&lt;p&gt;[^1]: https://github.com/open-telemetry/opentelemetry-…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5r5m-65gx-7vrh</guid>
    </item>
    <item>
      <title>gsd-2023-25151</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-25151</link>
      <description>gsd-2023-25151</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-25151</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-25151</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-25151</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:25.10: golang-opentelemetry-contrib, Ubuntu:26.04:LTS: golang-opentelemetry-contrib&lt;/p&gt;
&lt;p&gt;opentelemetry-go-contrib is a collection of extensions for OpenTelemetry-Go. The v0.38.0 release of `go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp` uses the `httpconv.ServerRequest` function to annotate metric measurements for the `http.server.request_content_length`, `http.server.response_content_length`, and `http.server.duration` instruments. The `ServerRequest` function sets the `http.target` attribute value to be the whole request URI (including the query string)[^1]. The metric instruments do not &amp;#34;forget&amp;#34; previous measurement attributes when `cumulative` temporality is used, this means the cardinality of the measurements allocated is directly correlated with the unique URIs handled. If the query string is constantly random, this will result in a constant increase in memory allocation that can be used in a denial-of-service attack. This issue has been addressed in version 0.39.0. Users are advised to upgrade. There are no known workarounds for this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:25.10: golang-opentelemetry-contrib, Ubuntu:26.04:LTS: golang-opentelemetry-contrib&lt;/p&gt;
&lt;p&gt;opentelemetry-go-contrib is a collection of extensions for OpenTelemetry-Go. The v0.38.0 release of `go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp` uses the `httpconv.ServerRequest` function to annotate metric measurements for the `http.server.request_content_length`, `http.server.response_content_length`, and `http.server.duration` instruments. The `ServerRequest` function sets the `http.target` attribute value to be the whole request URI (including the query string)[^1]. The metric instruments do not &amp;#34;forget&amp;#34; previous measurement attributes when `cumulative` temporality is used, this means the cardinality of the measurements allocated is directly correlated with the unique URIs handled. If the query string is constantly random, this will result in a constant increase in memory allocation that can be used in a denial-of-service attack. This issue has been addressed in version 0.39.0. Users are advised to upgrade. There are no known workarounds for this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-25151</guid>
    </item>
  </channel>
</rss>
