https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 30 Oct 2026 21:15:10 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-88879 <p>Traefik is an HTTP reverse proxy and load balancer. In Traefik v1.x, v2.x through v2.11.55, and v3.0.0 through v3.7.11, header names are canonicalized only on dashes, so X-Auth-User, X_Auth_User and X.Auth.User are treated as three distinct headers by Traefik, while backends that derive variable names from header names (CGI, WSGI, PHP, NGINX and others) collapse them into a single variable. A client can therefore smuggle a dot-form alias of a header that Traefik manages past the middleware managing it — for example supplying X.Authenticated.User alongside the canonical X-Authenticated-User written by the ForwardAuth middleware — causing such a backend to read the client-supplied value instead of the identity Traefik asserted. In the tested configuration (PHP 8.2 built-in SAPI over an HTTP/1 backend path), Go&#39;s lexical header ordering makes the attacker-supplied value win deterministically, so a client that ForwardAuth admits as a low-privilege identity can be treated by the backend as a different user or role. Any header Traefik sets is affected, not only ForwardAuth&#39;s. This is an incomplete fix for GHSA-x677-9fxg-v5c5, which blocked only the underscore form. Fixed in v2.11.56 and v3.7.12, which add the aliasHeadersStrategy entry-point option; because it defaults to &#39;keep&#39; for backwards compatibility, it must be explicitly set to &#39;delete&#39; or &#39;reject&#39; for the fix to take effect. Unmaintained release lines will not receive a patch.</p> <p>Traefik is an HTTP reverse proxy and load balancer. In Traefik v1.x, v2.x through v2.11.55, and v3.0.0 through v3.7.11, header names are canonicalized only on dashes, so X-Auth-User, X_Auth_User and X.Auth.User are treated as three distinct headers by Traefik, while backends that derive variable names from header names (CGI, WSGI, PHP, NGINX and others) collapse them into a single variable. A client can therefore smuggle a dot-form alias of a header that Traefik manages past the middleware managing it — for example supplying X.Authenticated.User alongside the canonical X-Authenticated-User written by the ForwardAuth middleware — causing such a backend to read the client-supplied value instead of the identity Traefik asserted. In the tested configuration (PHP 8.2 built-in SAPI over an HTTP/1 backend path), Go&#39;s lexical header ordering makes the attacker-supplied value win deterministically, so a client that ForwardAuth admits as a low-privilege identity can be treated by the backend as a different user or role. Any header Traefik sets is affected, not only ForwardAuth&#39;s. This is an incomplete fix for GHSA-x677-9fxg-v5c5, which blocked only the underscore form. Fixed in v2.11.56 and v3.7.12, which add the aliasHeadersStrategy entry-point option; because it defaults to &#39;keep&#39; for backwards compatibility, it must be explicitly set to &#39;delete&#39; or &#39;reject&#39; for the fix to take effect. Unmaintained release lines will not receive a patch.</p> https://db.gcve.eu/vuln/fkie_cve-2026-88879 https://db.gcve.eu/vuln/ghsa-cwr6-3wm2-9xhw <p>Traefik is an HTTP reverse proxy and load balancer. In Traefik v1.x, v2.x through v2.11.55, and v3.0.0 through v3.7.11, header names are canonicalized only on dashes, so X-Auth-User, X_Auth_User and X.Auth.User are treated as three distinct headers by Traefik, while backends that derive variable names from header names (CGI, WSGI, PHP, NGINX and others) collapse them into a single variable. A client can therefore smuggle a dot-form alias of a header that Traefik manages past the middleware managing it — for example supplying X.Authenticated.User alongside the canonical X-Authenticated-User written by the ForwardAuth middleware — causing such a backend to read the client-supplied value instead of the identity Traefik asserted. In the tested configuration (PHP 8.2 built-in SAPI over an HTTP/1 backend path), Go&#39;s lexical header ordering makes the attacker-supplied value win deterministically, so a client that ForwardAuth admits as a low-privilege identity can be treated by the backend as a different user or role. Any header Traefik sets is affected, not only ForwardAuth&#39;s. This is an incomplete fix for GHSA-x677-9fxg-v5c5, which blocked only the underscore form. Fixed in v2.11.56 and v3.7.12, which add the aliasHeadersStrategy entry-point option; because it defaults to &#39;keep&#39; for backwards compatibility, it must be explicitly set to &#39;delete&#39; or &#39;reject&#39; for the fix to take effect. Unmaintained release lines will not receive a patch.</p> <p>Traefik is an HTTP reverse proxy and load balancer. In Traefik v1.x, v2.x through v2.11.55, and v3.0.0 through v3.7.11, header names are canonicalized only on dashes, so X-Auth-User, X_Auth_User and X.Auth.User are treated as three distinct headers by Traefik, while backends that derive variable names from header names (CGI, WSGI, PHP, NGINX and others) collapse them into a single variable. A client can therefore smuggle a dot-form alias of a header that Traefik manages past the middleware managing it — for example supplying X.Authenticated.User alongside the canonical X-Authenticated-User written by the ForwardAuth middleware — causing such a backend to read the client-supplied value instead of the identity Traefik asserted. In the tested configuration (PHP 8.2 built-in SAPI over an HTTP/1 backend path), Go&#39;s lexical header ordering makes the attacker-supplied value win deterministically, so a client that ForwardAuth admits as a low-privilege identity can be treated by the backend as a different user or role. Any header Traefik sets is affected, not only ForwardAuth&#39;s. This is an incomplete fix for GHSA-x677-9fxg-v5c5, which blocked only the underscore form. Fixed in v2.11.56 and v3.7.12, which add the aliasHeadersStrategy entry-point option; because it defaults to &#39;keep&#39; for backwards compatibility, it must be explicitly set to &#39;delete&#39; or &#39;reject&#39; for the fix to take effect. Unmaintained release lines will not receive a patch.</p> https://db.gcve.eu/vuln/ghsa-cwr6-3wm2-9xhw https://db.gcve.eu/vuln/rhsa-2026:90321 <p>zod: zod: Denial of service via unbounded array validation axios: Axios: Server-Side Request Forgery and proxy bypass due to improper hostname normalization python-pip: Path traversal via malicious entry point name in pip wheel installation allows arbitrary file overwrite pacote: Pacote: Denial of Service via crafted spec.rawSpec value in addGitSha function bouncycastle: Bouncy Castle: Denial of Service via untrusted keystore length allocation undici: undici: Information disclosure and Denial of Service via malformed Cache-Control directives org.bouncycastle/bcprov-jdk15on: org.bouncycastle/bcprov-jdk18on: org.bouncycastle/bc-fips: org.bouncycastle/bctls-fips: Bouncy Castle for Java: Denial of Service due to unbounded memory allocation io.vertx/vertx-web: Eclipse Vert.x Web Client: Information disclosure via improper cookie domain validation io.quarkus/quarkus-rest: io.quarkus/quarkus-vertx-http: io.quarkus.resteasy.reactive/resteasy-reactive: Quarkus REST - Unbounded multipart MIME part-header accumulation allows remote OOM denial of service github.com/moby/go-archive: moby/go-archive: Arbitrary file write via link following in tar extraction @fastify/static: @fastify/static: Information disclosure via route guard bypass org.eclipse.jetty/jetty-http: Jetty: HTTP request smuggling via crafted chunked requests undici: undici: Denial of Service via unrequested WebSocket subprotocol net/mail: golang: Go net/mail: Denial of Service via crafted email inputs github.com/open-teleme…</p> <p>zod: zod: Denial of service via unbounded array validation axios: Axios: Server-Side Request Forgery and proxy bypass due to improper hostname normalization python-pip: Path traversal via malicious entry point name in pip wheel installation allows arbitrary file overwrite pacote: Pacote: Denial of Service via crafted spec.rawSpec value in addGitSha function bouncycastle: Bouncy Castle: Denial of Service via untrusted keystore length allocation undici: undici: Information disclosure and Denial of Service via malformed Cache-Control directives org.bouncycastle/bcprov-jdk15on: org.bouncycastle/bcprov-jdk18on: org.bouncycastle/bc-fips: org.bouncycastle/bctls-fips: Bouncy Castle for Java: Denial of Service due to unbounded memory allocation io.vertx/vertx-web: Eclipse Vert.x Web Client: Information disclosure via improper cookie domain validation io.quarkus/quarkus-rest: io.quarkus/quarkus-vertx-http: io.quarkus.resteasy.reactive/resteasy-reactive: Quarkus REST - Unbounded multipart MIME part-header accumulation allows remote OOM denial of service github.com/moby/go-archive: moby/go-archive: Arbitrary file write via link following in tar extraction @fastify/static: @fastify/static: Information disclosure via route guard bypass org.eclipse.jetty/jetty-http: Jetty: HTTP request smuggling via crafted chunked requests undici: undici: Denial of Service via unrequested WebSocket subprotocol net/mail: golang: Go net/mail: Denial of Service via crafted email inputs github.com/open-teleme…</p> https://db.gcve.eu/vuln/rhsa-2026:90321