Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Envoy Gateway Log Injection Vulnerability

CVSS 3.1 5.3 MEDIUMEUVD CVSS 3.1 5.3 CVSS 3.1 · [email protected] · Secondary 5.3 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by github.com/envoyproxy/gateway 1.2.7Fixed by github.com/envoyproxy/gateway 1.3.1osv · severity unknownFixed by github.com/envoyproxy/gateway 1.2.7Fixed by github.com/envoyproxy/gateway 1.3.1KEV status unknown

cve-program · CVE-2025-25294

Published

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.

Read the publisher's advisory

euvd · EUVD-2025-7667

Published

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.

Read the publisher's advisory

nvd · CVE-2025-25294

Published

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.

Read the publisher's advisory

osv · GHSA-mf24-chxh-hmvj

Published

### Impact 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. Examples of attacks include: - Using following string as user agent : `HELLO-WORLD", "evil-ip": "1.1.1.1", "x-forwarded-for": "1.1.1.1` would lead to setting of new access log properties and overwrite of existing properties. Existing properties such as the value of the X-Forwarded-For header may have importance for security analysis of access logs, and their overwrite can be used to hide malicious activity. - Using the following string as user-agent : `"` which renders an invalid json document. The invalid document may fail to be processed by observability solutions, which would allow attacker to hide malicious activity. ### Patches 1.3.1, 1.2.7 ### Fix Using JSON format as the default format for access logs. The logged document will contain the same key and values as before. Only the order of properties is different inside the logged document. ### Workaround One can overwrite the old text based default format with JSON formatter by setting the following property: "EnvoyProxy.spec.telemetry.[accessLog](https://gateway.envoyproxy.io/v1.3/api/extension_types/#proxyaccesslog)" to ``` settings: - format: type: JSON json: start_time: '%START_TIME%' method: '%REQ(:METHOD)%' x-envoy-origin-path: '%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)%' protocol: '%PROTOCOL%' response_code: '%RESPONSE_CODE%' response_flags: '%RESPONSE_FLAGS%' response_code_details: '%RESPONSE_CODE_DETAILS%' connection_termination_details: '%CONNECTION_TERMINATION_DETAILS%' upstream_transport_failure_reason: '%UPSTREAM_TRANSPORT_FAILURE_REASON%' bytes_received: '%BYTES_RECEIVED%' bytes_sent: '%BYTES_SENT%' duration: '%DURATION%' x-envoy-upstream-service-time: '%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)%' x-forwarded-for: '%REQ(X-FORWARDED-FOR)%' user-agent: '%REQ(USER-AGENT)%' x-request-id: '%REQ(X-REQUEST-ID)%' :authority: '%REQ(:AUTHORITY)%' upstream_host: '%UPSTREAM_HOST%' upstream_cluster: '%UPSTREAM_CLUSTER%' upstream_local_address: '%UPSTREAM_LOCAL_ADDRESS%' downstream_local_address: '%DOWNSTREAM_LOCAL_ADDRESS%' downstream_remote_address: '%DOWNSTREAM_REMOTE_ADDRESS%' requested_server_name: '%REQUESTED_SERVER_NAME%' route_name: '%ROUTE_NAME%' ``` see API definition [here](https://gateway.envoyproxy.io/v1.3/api/extension_types/#proxyaccesslogformat) ### References _Are there any links users can visit to find out more?_

Read the publisher's advisory

osv · GO-2025-3504

Published

Envoy Gateway Log Injection Vulnerability in github.com/envoyproxy/gateway

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.

CVE-2025-25294 · CVE overview and exploitation status

EUVD-2025-7667

GHSA-mf24-chxh-hmvj

BIT-envoy-gateway-2025-25294

GO-2025-3504

cve-program · CVE-2025-25294

euvd · EUVD-2025-7667

nvd · CVE-2025-25294

osv · GHSA-mf24-chxh-hmvj

osv · GO-2025-3504

Related changes

Linked by CVE identifier

No related changes are available here.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 18 Nov 02:26 UTC · 273 of 275 readable · 249 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current