Skip to content
Fencer Intel
medium 5.3

CVE-2025-25294 json

Envoy Gateway Log Injection Vulnerability

published last yr. modified last mo. also BIT-envoy-gateway-2025-25294 , EUVD-2025-7667 , GHSA-mf24-chxh-hmvj , GO-2025-3504

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 21%
public exploits
0
none known

Summary

Envoy Gateway is an open source project for managing Envoy Proxy as a standalone or Kubernetes-based application gateway. In all Envoy Gateway versions prior to 1.2.7 and 1.3.1 a default Envoy Proxy access log configuration is used. This format is vulnerable to log injection attacks. If the attacker uses a specially crafted user-agent which performs json injection, then he could add and overwrite fields to the access log. This vulnerability is fixed in 1.3.1 and 1.2.7. One can overwrite the old text based default format with JSON formatter by modifying the "EnvoyProxy.spec.telemetry.accessLog" setting.

Patch / fix

  • go github.com/envoyproxy/gateway 1.2.7, 1.3.1
  • bitnami envoy-gateway 1.2.7, 1.3.1
  • envoyproxy gateway 1.2.7, 1.3.1
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250312T181707-1.1

opensuse advisories openSUSE-SU-2025:14889-1

Is CVE-2025-25294 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-25294 updated cvss 5.3

envoyproxy/gateway: Envoy Gateway Log Injection Vulnerability

  • Red Hat Connectivity Link 1 rhcl-operator-container, rhcl-operator-bundle-container
    affected: no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/envoyproxy/gateway
<1.2.7
>=1.3.0-rc.1, <1.3.1
1.2.7
1.3.1
bitnami envoy-gateway
<1.2.7
>=1.3.0, <1.3.1
1.2.7
1.3.1

Affected products

  • envoyproxy gateway

Classification

Weakness
  • CWE-117 Improper Output Neutralization for Logs

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.