Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-56cj-wgg3-x943 | Envoy affected by off-by-one write in JsonEscaper::escapeString() |
Wed, 11 Mar 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:* cpe:2.3:a:envoyproxy:envoy:1.37.0:*:*:*:*:*:*:* |
Wed, 11 Mar 2026 12:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Envoyproxy
Envoyproxy envoy |
|
| Vendors & Products |
Envoyproxy
Envoyproxy envoy |
Tue, 10 Mar 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 10 Mar 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Envoy has an off-by-one write in JsonEscaper::escapeString() | |
| Weaknesses | CWE-193 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-03-10T20:12:40.483Z
Reserved: 2026-02-13T16:27:51.805Z
Link: CVE-2026-26309
Updated: 2026-03-10T20:11:56.525Z
Status : Analyzed
Published: 2026-03-10T20:16:35.880
Modified: 2026-03-11T16:14:20.730
Link: CVE-2026-26309
No data.
OpenCVE Enrichment
Updated: 2026-04-16T09:45:31Z
Github GHSA