<?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>Sat, 03 Oct 2026 09:12:34 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-0958 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0958</link>
      <description>certfr-2026-avi-0958</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0958</guid>
    </item>
    <item>
      <title>Withdrawn: CLEANSTART-2026-CL03013 — Netty is an asynchronous, event-driven network application framework</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-cl03013</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: apache-hive&lt;/p&gt;
&lt;p&gt;Multiple security vulnerabilities affect the apache-hive package. Netty is an asynchronous, event-driven network application framework. See references for individual vulnerability details.&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: apache-hive&lt;/p&gt;
&lt;p&gt;Multiple security vulnerabilities affect the apache-hive package. Netty is an asynchronous, event-driven network application framework. See references for individual vulnerability details.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-cl03013</guid>
    </item>
    <item>
      <title>EUVD-2026-370196</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-370196</link>
      <description>EUVD-2026-370196</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-370196</guid>
    </item>
    <item>
      <title>fkie_cve-2026-45292</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-45292</link>
      <description>&lt;p&gt;opentelemetry-java is the Java implementation of the OpenTelemetry API for recording telemetry, and SDK for managing telemetry recorded by the API. Prior to 1.62.0, a vulnerability affects the baggage propagation implementation in opentelemetry-api and opentelemetry-extension-trace-propagators. Parsing oversized baggage causes unbounded memory allocation and CPU consumption. Because baggage is automatically re-injected into every outgoing request, the effect can fan out to downstream services that never received the original malicious request. This vulnerability is fixed in 1.62.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;opentelemetry-java is the Java implementation of the OpenTelemetry API for recording telemetry, and SDK for managing telemetry recorded by the API. Prior to 1.62.0, a vulnerability affects the baggage propagation implementation in opentelemetry-api and opentelemetry-extension-trace-propagators. Parsing oversized baggage causes unbounded memory allocation and CPU consumption. Because baggage is automatically re-injected into every outgoing request, the effect can fan out to downstream services that never received the original malicious request. This vulnerability is fixed in 1.62.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-45292</guid>
    </item>
    <item>
      <title>GHSA-rcgg-9c38-7xpx — OpenTelemetry Java SDK has Unbounded Memory Allocation in W3C Baggage Propagation</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rcgg-9c38-7xpx</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: io.opentelemetry:opentelemetry-api, Maven: io.opentelemetry:opentelemetry-extension-trace-propagators&lt;/p&gt;
&lt;p&gt;## Overview&lt;/p&gt;
&lt;p&gt;A vulnerability affects the baggage propagation implementation in
`opentelemetry-api` and `opentelemetry-extension-trace-propagators`. Parsing oversized baggage
causes unbounded memory allocation and CPU consumption. Because baggage is automatically
re-injected into every outgoing request, the effect can fan out to downstream services that
never received the original malicious request.&lt;/p&gt;
&lt;p&gt;## Technical Details&lt;/p&gt;
&lt;p&gt;- `W3CBaggagePropagator` did not enforce any limit on the total size or entry count of the
  `baggage` header. The parser iterated character-by-character through the entire value
  regardless of length.
- `JaegerPropagator` and `OtTracePropagator` had the same gap in their respective baggage
  extraction paths.
- The W3C Baggage specification recommends a maximum of 8,192 bytes and 180 entries; none of
  these limits were enforced.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;The practical availability impact for most deployments is limited. Every major Java HTTP server
enforces its own header size limit (Tomcat, Jetty, Netty, Vert.x, and gRPC-Java all default to
8 KiB), constraining what an external attacker can deliver before the application is reached.
The risk is higher when transport-layer limits are absent — e.g., a compromised internal service
communicating over a non-HTTP or custom transport.&lt;/p&gt;
&lt;p&gt;## Remediation&lt;/p&gt;
&lt;p&gt;Update to version 1.62.0 or later ([#8380](https://github.com/open-telemetry/opentelemetry-java/pull/8380)).
The fix enforces limits consistent with the W3C Baggage specificati…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: io.opentelemetry:opentelemetry-api, Maven: io.opentelemetry:opentelemetry-extension-trace-propagators&lt;/p&gt;
&lt;p&gt;## Overview&lt;/p&gt;
&lt;p&gt;A vulnerability affects the baggage propagation implementation in
`opentelemetry-api` and `opentelemetry-extension-trace-propagators`. Parsing oversized baggage
causes unbounded memory allocation and CPU consumption. Because baggage is automatically
re-injected into every outgoing request, the effect can fan out to downstream services that
never received the original malicious request.&lt;/p&gt;
&lt;p&gt;## Technical Details&lt;/p&gt;
&lt;p&gt;- `W3CBaggagePropagator` did not enforce any limit on the total size or entry count of the
  `baggage` header. The parser iterated character-by-character through the entire value
  regardless of length.
- `JaegerPropagator` and `OtTracePropagator` had the same gap in their respective baggage
  extraction paths.
- The W3C Baggage specification recommends a maximum of 8,192 bytes and 180 entries; none of
  these limits were enforced.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;The practical availability impact for most deployments is limited. Every major Java HTTP server
enforces its own header size limit (Tomcat, Jetty, Netty, Vert.x, and gRPC-Java all default to
8 KiB), constraining what an external attacker can deliver before the application is reached.
The risk is higher when transport-layer limits are absent — e.g., a compromised internal service
communicating over a non-HTTP or custom transport.&lt;/p&gt;
&lt;p&gt;## Remediation&lt;/p&gt;
&lt;p&gt;Update to version 1.62.0 or later ([#8380](https://github.com/open-telemetry/opentelemetry-java/pull/8380)).
The fix enforces limits consistent with the W3C Baggage specificati…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rcgg-9c38-7xpx</guid>
    </item>
    <item>
      <title>NCSC-2026-0326 — Kwetsbaarheden verholpen in Keycloak</title>
      <link>https://cve.radiocsirt.org/vuln/ncsc-2026-0326</link>
      <description>NCSC-2026-0326</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ncsc-2026-0326</guid>
    </item>
    <item>
      <title>RHSA-2026:28573 — Red Hat Security Advisory: Red Hat Offline Knowledge Portal security and content update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:28573</link>
      <description>&lt;p&gt;org.eclipse.jetty.ee10/jetty-ee10: early return from the JASPIAuthenticator class without clearing ThreadLocal variables netty-handler: netty-handler: IPv6 subnet rule bypass due to incorrect masking operation opentelemetry-java: opentelemetry-api: opentelemetry-extension-trace-propagators: OpenTelemetry Java: Denial of Service due to unbounded memory allocation when parsing oversized baggage netty-handler: Netty: Denial of Service due to eager buffer allocation in TLS handshake netty-handler: Netty: Improper trust manager handling leads to hostname verification bypass&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;org.eclipse.jetty.ee10/jetty-ee10: early return from the JASPIAuthenticator class without clearing ThreadLocal variables netty-handler: netty-handler: IPv6 subnet rule bypass due to incorrect masking operation opentelemetry-java: opentelemetry-api: opentelemetry-extension-trace-propagators: OpenTelemetry Java: Denial of Service due to unbounded memory allocation when parsing oversized baggage netty-handler: Netty: Denial of Service due to eager buffer allocation in TLS handshake netty-handler: Netty: Improper trust manager handling leads to hostname verification bypass&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:28573</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2242 — IBM Operational Decision Manager: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2242</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM Operational Decision Manager ausnutzen, um Sicherheitsbeschränkungen zu umgehen, um einen Denial of Service zu verursachen und Code auszuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM Operational Decision Manager ausnutzen, um Sicherheitsbeschränkungen zu umgehen, um einen Denial of Service zu verursachen und Code auszuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2242</guid>
    </item>
  </channel>
</rss>
