<?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://db.gcve.eu</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>Thu, 29 Oct 2026 17:47:52 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-116694</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-116694</link>
      <description>&lt;p&gt;OpenTelemetry Python provides the Python API and SDK for OpenTelemetry. Prior to 1.45.0, JaegerPropagator.extract() in opentelemetry-propagator-jaeger processes inbound uberctx-* baggage values without entry, per-entry byte, or total-byte limits. Services that enable the optional Jaeger propagator can perform unnecessary CPU work and short-lived heap allocations when an untrusted carrier supplies numerous or oversized values, contributing to denial of service when transport-level limits do not constrain the input. Common default Python HTTP server limits reduce the practical impact, while custom getters, non-HTTP transports, or raised header limits increase exposure. This issue is fixed in version 1.45.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenTelemetry Python provides the Python API and SDK for OpenTelemetry. Prior to 1.45.0, JaegerPropagator.extract() in opentelemetry-propagator-jaeger processes inbound uberctx-* baggage values without entry, per-entry byte, or total-byte limits. Services that enable the optional Jaeger propagator can perform unnecessary CPU work and short-lived heap allocations when an untrusted carrier supplies numerous or oversized values, contributing to denial of service when transport-level limits do not constrain the input. Common default Python HTTP server limits reduce the practical impact, while custom getters, non-HTTP transports, or raised header limits increase exposure. This issue is fixed in version 1.45.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-116694</guid>
    </item>
    <item>
      <title>GHSA-f5m9-jfrj-jjj7 — OpenTelemetry Python: Unbounded memory allocation in Jaeger baggage propagation</title>
      <link>https://db.gcve.eu/vuln/ghsa-f5m9-jfrj-jjj7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: opentelemetry-propagator-jaeger&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`JaegerPropagator.extract()` in `opentelemetry-propagator-jaeger` did not enforce limits when extracting inbound `uberctx-*` baggage headers. Attacker-controlled baggage could cause unnecessary CPU work and short-lived heap allocations while processing more data than the propagator should accept.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Services that enable the optional Jaeger propagator and accept untrusted inbound propagation headers may experience increased per-request resource usage. This can contribute to denial-of-service risk when transport-level limits are absent or configured above the baggage limits.&lt;/p&gt;
&lt;p&gt;The practical impact for most Python web deployments is limited. The package must be installed separately, and the Jaeger propagator is not enabled by the default OpenTelemetry Python configuration.&lt;/p&gt;
&lt;p&gt;Common Python web servers also constrain request headers before they reach the propagator:&lt;/p&gt;
&lt;p&gt;- Gunicorn allows a maximum of 100 request-header fields and 8,190 bytes per field by default.
- Uvicorn’s h11 implementation limits its incomplete-event buffer to 16,384 bytes by default.&lt;/p&gt;
&lt;p&gt;The risk is higher for non-HTTP transports, custom `TextMapGetter` implementations, or deployments where server and gateway limits have been increased or disabled.&lt;/p&gt;
&lt;p&gt;The impact is limited to availability. This issue does not expose or modify telemetry data and does not allow code execution.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Versions of `opentelemetry-propagator-jaeger` earlier than `1.45.0` are affected.&lt;/p&gt;
&lt;p&gt;Upgrade `opentelemetry-propa…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: opentelemetry-propagator-jaeger&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`JaegerPropagator.extract()` in `opentelemetry-propagator-jaeger` did not enforce limits when extracting inbound `uberctx-*` baggage headers. Attacker-controlled baggage could cause unnecessary CPU work and short-lived heap allocations while processing more data than the propagator should accept.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Services that enable the optional Jaeger propagator and accept untrusted inbound propagation headers may experience increased per-request resource usage. This can contribute to denial-of-service risk when transport-level limits are absent or configured above the baggage limits.&lt;/p&gt;
&lt;p&gt;The practical impact for most Python web deployments is limited. The package must be installed separately, and the Jaeger propagator is not enabled by the default OpenTelemetry Python configuration.&lt;/p&gt;
&lt;p&gt;Common Python web servers also constrain request headers before they reach the propagator:&lt;/p&gt;
&lt;p&gt;- Gunicorn allows a maximum of 100 request-header fields and 8,190 bytes per field by default.
- Uvicorn’s h11 implementation limits its incomplete-event buffer to 16,384 bytes by default.&lt;/p&gt;
&lt;p&gt;The risk is higher for non-HTTP transports, custom `TextMapGetter` implementations, or deployments where server and gateway limits have been increased or disabled.&lt;/p&gt;
&lt;p&gt;The impact is limited to availability. This issue does not expose or modify telemetry data and does not allow code execution.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Versions of `opentelemetry-propagator-jaeger` earlier than `1.45.0` are affected.&lt;/p&gt;
&lt;p&gt;Upgrade `opentelemetry-propa…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-f5m9-jfrj-jjj7</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-116694</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-116694</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.10: python-opentelemetry, Ubuntu:26.04:LTS: python-opentelemetry&lt;/p&gt;
&lt;p&gt;OpenTelemetry Python provides the Python API and SDK for OpenTelemetry. Prior to 1.45.0, JaegerPropagator.extract() in opentelemetry-propagator-jaeger processes inbound uberctx-* baggage values without entry, per-entry byte, or total-byte limits. Services that enable the optional Jaeger propagator can perform unnecessary CPU work and short-lived heap allocations when an untrusted carrier supplies numerous or oversized values, contributing to denial of service when transport-level limits do not constrain the input. Common default Python HTTP server limits reduce the practical impact, while custom getters, non-HTTP transports, or raised header limits increase exposure. This issue is fixed in version 1.45.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.10: python-opentelemetry, Ubuntu:26.04:LTS: python-opentelemetry&lt;/p&gt;
&lt;p&gt;OpenTelemetry Python provides the Python API and SDK for OpenTelemetry. Prior to 1.45.0, JaegerPropagator.extract() in opentelemetry-propagator-jaeger processes inbound uberctx-* baggage values without entry, per-entry byte, or total-byte limits. Services that enable the optional Jaeger propagator can perform unnecessary CPU work and short-lived heap allocations when an untrusted carrier supplies numerous or oversized values, contributing to denial of service when transport-level limits do not constrain the input. Common default Python HTTP server limits reduce the practical impact, while custom getters, non-HTTP transports, or raised header limits increase exposure. This issue is fixed in version 1.45.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-116694</guid>
    </item>
  </channel>
</rss>
