<?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-10-03T21:17:48.772307+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/bit-envoy-2026-26309</id>
    <title>BIT-envoy-2026-26309 — Envoy has an off-by-one write in JsonEscaper::escapeString()</title>
    <updated>2026-10-03T21:17:48.777510+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: envoy</p>
<p>Envoy is a high-performance edge/middle/service proxy. Prior to 1.37.1, 1.36.5, 1.35.8, and 1.34.13, an off-by-one write in Envoy::JsonEscaper::escapeString() can corrupt std::string null-termination, causing undefined behavior and potentially leading to crashes or out-of-bounds reads when the resulting string is later treated as a C-string. This vulnerability is fixed in 1.37.1, 1.36.5, 1.35.8, and 1.34.13.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-envoy-2026-26309"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-275356</id>
    <title>EUVD-2026-275356</title>
    <updated>2026-10-03T21:17:48.777562+00:00</updated>
    <content>EUVD-2026-275356</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-275356"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-26309</id>
    <title>fkie_cve-2026-26309</title>
    <updated>2026-10-03T21:17:48.777579+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Envoy is a high-performance edge/middle/service proxy. Prior to 1.37.1, 1.36.5, 1.35.8, and 1.34.13, an off-by-one write in Envoy::JsonEscaper::escapeString() can corrupt std::string null-termination, causing undefined behavior and potentially leading to crashes or out-of-bounds reads when the resulting string is later treated as a C-string. This vulnerability is fixed in 1.37.1, 1.36.5, 1.35.8, and 1.34.13.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-26309"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-56cj-wgg3-x943</id>
    <title>GHSA-56cj-wgg3-x943 — Envoy affected by off-by-one write in JsonEscaper::escapeString()</title>
    <updated>2026-10-03T21:17:48.777602+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/envoyproxy/envoy</p>
<p>### Summary</p>
<p>An off-by-one write in Envoy::JsonEscaper::escapeString() can corrupt
  std::string null-termination, causing undefined behavior and potentially
  leading to crashes or out-of-bounds reads when the resulting string is later
  treated as a C-string.</p>
<p>### Details</p>
<p>The bug is in the control-character escaping path in source/common/common/
  json_escape_string.h:67.</p>
<p>- The function pre-sizes result to the final length: std::string
    result(input.size() + required_size, '\\');
  - For control characters (0x00..0x1f), it emits a JSON escape sequence of
    length 6: \u00XX.
  - It uses sprintf(&amp;result[position + 1], "u%04x", ...), which writes 5 chars +
    a trailing NUL (\0) starting at result[position + 1].
  - Then it does position += 6; and writes result[position] = '\\'; to overwrite
    the NUL.
  - If the control character occurs at the end of the output (e.g., the input
    ends with \x01), then after position += 6, position == result.size(), so
    result[position] is one past the end (off-by-one), violating std::string
    bounds/contract.</p>
<p>Concretely, the problematic lines are:</p>
<p>- source/common/common/json_escape_string.h:69 (sprintf(...))
  - source/common/common/json_escape_string.h:72 (result[position] = '\\';)</p>
<p>Potentially reachable from request-driven paths that escape untrusted data,
  e.g. invalid header reporting:</p>
<p>- source/common/http/header_utility.cc:538 ~ source/common/http/
    header_utility.cc:546 (escapes invalid header ke…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-56cj-wgg3-x943"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0704</id>
    <title>WID-SEC-W-2026-0704 — Google Cloud Platform Envoy Proxy, Istio und Service Mesh: Mehrere Schwachstellen</title>
    <updated>2026-10-03T21:17:48.777663+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in Google Cloud Platform ausnutzen, um Sicherheitsvorkehrungen zu umgehen, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0704"/>
  </entry>
</feed>
