CVE-2026-88009
Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging
Traefik is an open source HTTP reverse proxy and load balancer. Prior to 2.11.57, and 3.7.13, Traefik accepts a rootless HTTP/1 request target that Go stores in URL.Opaque while leaving URL.Path empty. The rewriteRequestBuilder path evaluates routing, path sanitization, forwardAuth, encodedCharacters, and access logging against a path normalized to / but forwards URL.Opaque verbatim to the backend, allowing cross-vhost routing bypass, path-scoped authorization bypass, and access-log evasion when the backend interprets the opaque target as a path. This issue is fixed in 2.11.57 and 3.7.13.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
8.8
Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging
Traefik is an open source HTTP reverse proxy and load balancer. Prior to 2.11.57, and 3.7.13, Traefik accepts a rootless HTTP/1 request target that Go stores in URL.Opaque while leaving URL.Path empty. The rewriteRequestBuilder path evaluates routing, path sanitization, forwardAuth, encodedCharacters, and access logging against a path normalized to / but forwards URL.Opaque verbatim to the backend, allowing cross-vhost routing bypass, path-scoped authorization bypass, and access-log evasion when the backend interprets the opaque target as a path. This issue is fixed in 2.11.57 and 3.7.13.
- Record
CVE-2026-88009- CVSS 4.0
- 8.8 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N - Weakness
- CWE-444, CWE-1286
- Updated
- 2026-11-02
EUVDEUVD-2026-75578
8.8
Traefik is an open source HTTP reverse proxy and load balancer. Prior to 2.11.57, and 3.7.13, Traefik accepts a rootless HTTP/1 request target that Go stores in URL.Opaque while leaving URL.Path empty. The rewriteRequestBuilder path evaluates routing, path sanitization, forwardAuth, encodedCharacters, and access logging against a path normalized to / but forwards URL.Opaque verbatim to the backend, allowing cross-vhost routing bypass, path-scoped authorization bypass, and access-log evasion when the backend interprets the opaque target as a path. This issue is fixed in 2.11.57 and 3.7.13.
- Record
EUVD-2026-75578- CVSS 4.0
- 8.8 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-f52w-8j3h-j724
8.8
Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging
Summary
Traefik accepts an HTTP/1.x request whose request-target is in rootless / opaque form (for example GET http:http://internal-vhost/admin HTTP/1.1). Go parses this into URL.Opaque with an empty URL.Path, so Traefik evaluates all routing, path-sanitization, middleware and access-log decisions against a path that normalizes to /, while the proxy forwards the attacker's original target byte-for-byte to the backend. Router path/prefix guards, forwardAuth path-scoped policies and the encodedCharacters hardening never see the real target, and the access log records every such request as GET / HTTP/1.1. Against a backend that resolves a rootless target as a path, this yields cross-vhost routing bypass, path-scoped authorization bypass and access-log evasion — unauthenticated, with stock entrypoint defaults.
Traefik v3.0 through v3.6 are end-of-life and are also affected; they will not receive a fix on their own line. Users on those versions must upgrade to v3.7.13.
Patches
- https://github.com/traefik/traefik/releases/tag/v2.11.57
- https://github.com/traefik/traefik/releases/tag/v3.7.13
For more information
If you have any questions or comments about this advisory, please open an issue.
<details> <summary>Original Description</summary>
Summary
The scanner claims rewriteRequestBuilder (pkg/proxy/httputil/proxy.go:97) rebuilds the outbound target from URL.Path / RawPath / RawQuery but never clears URL.Opaque, so a client sending a rootless request-target (GET http:http://internal-vhost/admin HTTP/1.1) has that byte string written verbatim into the backend request line while Traefik routes, sanitizes, guards and logs an empty path.
The claim is correct in every load-bearing detail, and it reproduces end to end on the GA image traefik:v3.7 (v3.7.9, go1.26.5) with stock entrypoint defaults. Three separate consequences were observed on the wire, not inferred:
- Cross-vhost routing bypass. Traefik matched
Host(app.example.com), nginx served theinternal-vhostserver block. - Path-scoped authorization bypass. A
forwardAuthguard that denies^/adminreturnedDENYfor/adminandALLOWfor the opaque form of the same request, which then reached/adminon the backend. - Access-log evasion. All three requests, benign and malicious, were logged identically as
"GET / HTTP/1.1".
Plus a fourth that is decisive against the usual closure argument: the documented opt-in hardening encodedCharacters.allowEncodedSlash=false rejects the canonical /admin%2f..%2fsecret with 400, and does not fire at all on the opaque form carrying the identical payload.
This is not the "the operator left an opt-in permissive" shape that lesson L-012 and guideline G-03 teach us to decline. The hardening is enabled and is structurally bypassed.
Affected code
pkg/proxy/httputil/proxy.go:97(rewriteRequestBuilder)pkg/muxer/http/mux.go:139(withRoutingPath)
Code analysis
The sink
pkg/proxy/httputil/proxy.go:87-105 sets Scheme, Host, Path, RawPath, RawQuery on pr.Out.URL and clears pr.Out.RequestURI. It never touches pr.Out.URL.Opaque, which httputil.ReverseProxy carried over from the inbound request clone:
pr.Out.URL.Scheme = target.Scheme
pr.Out.URL.Host = target.Host
...
pr.Out.URL.Path = u.Path
pr.Out.URL.RawPath = u.RawPath
...
pr.Out.RequestURI = "" // Outgoing request should not have RequestURI
net/http's Request.write then does ruri := r.URL.RequestURI(), and url.URL.RequestURI() returns Opaque in preference to the escaped path whenever Opaque != "". So the wire target is the attacker's string, and every field the proxy carefully set is ignored.
How Opaque gets populated
net/http's readRequest ($GOROOT/src/net/http/request.go:1104-1127) applies no origin-form check: it calls url.ParseRequestURI(rawurl) directly, and the only special…
- Record
GHSA-f52w-8j3h-j724- CVSS 4.0
- 8.8 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N - Weakness
- CWE-444, CWE-1286
- Updated
- 2026-11-02
NVD
8.8
Traefik is an open source HTTP reverse proxy and load balancer. Prior to 2.11.57, and 3.7.13, Traefik accepts a rootless HTTP/1 request target that Go stores in URL.Opaque while leaving URL.Path empty. The rewriteRequestBuilder path evaluates routing, path sanitization, forwardAuth, encodedCharacters, and access logging against a path normalized to / but forwards URL.Opaque verbatim to the backend, allowing cross-vhost routing bypass, path-scoped authorization bypass, and access-log evasion when the backend interprets the opaque target as a path. This issue is fixed in 2.11.57 and 3.7.13.
- Record
CVE-2026-88009- CVSS 4.0
- 8.8 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - CVSS 3.1
- 8.2 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N - Weakness
- CWE-444, CWE-1286
- Updated
- 2026-11-02
OSV
8.8
Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging
Traefik is an open source HTTP reverse proxy and load balancer. Prior to 2.11.57, and 3.7.13, Traefik accepts a rootless HTTP/1 request target that Go stores in URL.Opaque while leaving URL.Path empty. The rewriteRequestBuilder path evaluates routing, path sanitization, forwardAuth, encodedCharacters, and access logging against a path normalized to / but forwards URL.Opaque verbatim to the backend, allowing cross-vhost routing bypass, path-scoped authorization bypass, and access-log evasion when the backend interprets the opaque target as a path. This issue is fixed in 2.11.57 and 3.7.13.
- Record
CVE-2026-88009- CVSS 4.0
- 8.8 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N - Weakness
- CWE-1286, CWE-444
- Updated
- 2026-11-02
OSVGHSA-f52w-8j3h-j724
8.8
Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging
Summary
Traefik accepts an HTTP/1.x request whose request-target is in rootless / opaque form (for example GET http:http://internal-vhost/admin HTTP/1.1). Go parses this into URL.Opaque with an empty URL.Path, so Traefik evaluates all routing, path-sanitization, middleware and access-log decisions against a path that normalizes to /, while the proxy forwards the attacker's original target byte-for-byte to the backend. Router path/prefix guards, forwardAuth path-scoped policies and the encodedCharacters hardening never see the real target, and the access log records every such request as GET / HTTP/1.1. Against a backend that resolves a rootless target as a path, this yields cross-vhost routing bypass, path-scoped authorization bypass and access-log evasion — unauthenticated, with stock entrypoint defaults.
Traefik v3.0 through v3.6 are end-of-life and are also affected; they will not receive a fix on their own line. Users on those versions must upgrade to v3.7.13.
Patches
- https://github.com/traefik/traefik/releases/tag/v2.11.57
- https://github.com/traefik/traefik/releases/tag/v3.7.13
For more information
If you have any questions or comments about this advisory, please open an issue.
<details> <summary>Original Description</summary>
Summary
The scanner claims rewriteRequestBuilder (pkg/proxy/httputil/proxy.go:97) rebuilds the outbound target from URL.Path / RawPath / RawQuery but never clears URL.Opaque, so a client sending a rootless request-target (GET http:http://internal-vhost/admin HTTP/1.1) has that byte string written verbatim into the backend request line while Traefik routes, sanitizes, guards and logs an empty path.
The claim is correct in every load-bearing detail, and it reproduces end to end on the GA image traefik:v3.7 (v3.7.9, go1.26.5) with stock entrypoint defaults. Three separate consequences were observed on the wire, not inferred:
- Cross-vhost routing bypass. Traefik matched
Host(app.example.com), nginx served theinternal-vhostserver block. - Path-scoped authorization bypass. A
forwardAuthguard that denies^/adminreturnedDENYfor/adminandALLOWfor the opaque form of the same request, which then reached/adminon the backend. - Access-log evasion. All three requests, benign and malicious, were logged identically as
"GET / HTTP/1.1".
Plus a fourth that is decisive against the usual closure argument: the documented opt-in hardening encodedCharacters.allowEncodedSlash=false rejects the canonical /admin%2f..%2fsecret with 400, and does not fire at all on the opaque form carrying the identical payload.
This is not the "the operator left an opt-in permissive" shape that lesson L-012 and guideline G-03 teach us to decline. The hardening is enabled and is structurally bypassed.
Affected code
pkg/proxy/httputil/proxy.go:97(rewriteRequestBuilder)pkg/muxer/http/mux.go:139(withRoutingPath)
Code analysis
The sink
pkg/proxy/httputil/proxy.go:87-105 sets Scheme, Host, Path, RawPath, RawQuery on pr.Out.URL and clears pr.Out.RequestURI. It never touches pr.Out.URL.Opaque, which httputil.ReverseProxy carried over from the inbound request clone:
pr.Out.URL.Scheme = target.Scheme
pr.Out.URL.Host = target.Host
...
pr.Out.URL.Path = u.Path
pr.Out.URL.RawPath = u.RawPath
...
pr.Out.RequestURI = "" // Outgoing request should not have RequestURI
net/http's Request.write then does ruri := r.URL.RequestURI(), and url.URL.RequestURI() returns Opaque in preference to the escaped path whenever Opaque != "". So the wire target is the attacker's string, and every field the proxy carefully set is ignored.
How Opaque gets populated
net/http's readRequest ($GOROOT/src/net/http/request.go:1104-1127) applies no origin-form check: it calls url.ParseRequestURI(rawurl) directly, and the only special…
- Record
GHSA-f52w-8j3h-j724- CVSS 4.0
- 8.8 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N - Weakness
- CWE-1286, CWE-444
- Updated
- 2026-11-02
Show 5 moreShow less
OSVGO-2026-6465 No score
Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging in github.com/traefik/traefik
Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging in github.com/traefik/traefik
- Record
GO-2026-6465- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:12076-1 No score
traefik-3.7.13-1.1 on GA media
These are all security issues fixed in the traefik-3.7.13-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:12076-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21897-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
Changes for govulncheck-vulndb:
- Update to version 0.0.20260916T180043 2026-09-16T18:00:43Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-6348 CVE-2026-84304 GHSA-vp52-pcj8-j9qc
- GO-2026-6356 CVE-2026-65959 GHSA-mhc4-g3wh-cw7m
- GO-2026-6366 CVE-2026-61625 GHSA-8q3c-rjr9-xxrp
- GO-2026-6372 CVE-2026-79921 GHSA-6c5v-hqjr-5xxp
- GO-2026-6441 CVE-2026-84303 GHSA-qc2q-p7wx-3px3
- GO-2026-6443 CVE-2026-84445 GHSA-2v4p-qf9q-27wj
- GO-2026-6444 CVE-2026-53495 GHSA-7jxh-36q5-gcqv
- GO-2026-6445 CVE-2025-58363 GHSA-c23q-fw86-9h5x
- GO-2026-6446 CVE-2025-24978 GHSA-g8rh-fjm6-h2h9
- GO-2026-6447 CVE-2025-24979 GHSA-pqqc-8v73-9gg2
- GO-2026-6448 CVE-2026-59185 GHSA-cp3j-m783-3ph5
- GO-2026-6449 GHSA-hxjg-93wc-h8p8
- GO-2026-6450 CVE-2026-59172 GHSA-m835-3cm9-rggg
- GO-2026-6451 CVE-2026-59157 GHSA-v25g-mvwr-f5fp
- GO-2026-6452 CVE-2026-59162 GHSA-fx5j-qcqg-grpf
- GO-2026-6453 CVE-2026-59161 GHSA-q5j5-6p94-4gwc
- GO-2026-6454 CVE-2026-88012 GHSA-7ghq-v6jf-g56c
- GO-2026-6455 CVE-2026-88011 GHSA-rf44-j88r-hh8c
- GO-2026-6456 CVE-2026-88045 GHSA-2p48-j3qc-rx9f
- GO-2026-6457 CVE-2026-88046 GHSA-38xv-hf3p-h7mq
- GO-2026-6458 CVE-2026-88017 GHSA-c476-6w5q-jw77
- GO-2026-6459 CVE-2026-88016 GHSA-f8g7-2xjc-7mfh
- GO-2026-6460 CVE-2026-88044 GHSA-p569-5gjg-9cmj
- GO-2026-6461 CVE-2026-88015 GHSA-p6m2-r3w9-mpxw
- GO-2026-6462 CVE-2026-88018 GHSA-xwwr-4h3p-r22c
- GO-2026-6463 CVE-2026-88013 GHSA-486v-q2wf-fp2r
- GO-2026-6464 CVE-2026-88014 GHSA-66hp-wgxq-6f5q
- GO-2026-6465 CVE-2026-88009 GHSA-f52w-8j3h-j724
- GO-2026-6466 CVE-2026-88007 GHSA-qqjf-53cj-pwvv
- GO-2026-6467 CVE-2026-88004 GHSA-v67p-phpq-fc8x
- GO-2026-6468 CVE-2026-88008 GHSA-w4v4-9rw7-5326
- GO-2026-6469 CVE-2026-56665 GHSA-v77h-2w3m-94hx
- GO-2026-6470 CVE-2026-56666 GHSA-992q-9gwp-7r79
- GO-2026-6473 CVE-2026-76081 GHSA-v859-c572-qh5p
- GO-2026-6474 CVE-2026-56668 GHSA-vrh8-c9cm-wh8v
- Update to version 0.0.20260910T144842 2026-09-10T14:48:42Z.
- GO-2026-6302 GHSA-mf7q-r4rv-jv94
- GO-2026-6343 CVE-2026-25782 GHSA-qm72-8prh-g92x
- GO-2026-6344 CVE-2026-26292 GHSA-rc56-rj3f-xggf
- GO-2026-6345 CVE-2026-27779 GHSA-v8f2-2ghq-9whv
- GO-2026-6346 CVE-2026-27780 GHSA-vhq7-fwwh-7hjf
- GO-2026-6347 CVE-2026-27660 GHSA-x92v-f5gc-r34v
- GO-2026-6350 CVE-2026-59832 GHSA-275h-v5h9-vr82
- GO-2026-6351 CVE-2026-72920 GHSA-2v6v-25fm-p4fg
- GO-2026-6353 CVE-2026-59834 GHSA-h89q-4j2h-7h88
- GO-2026-6357 CVE-2026-73667 GHSA-2mw5-23gm-pccq
- GO-2026-6358 CVE-2026-73841 GHSA-52gf-6rpq-fgmx
- GO-2026-6359 CVE-2026-67446 GHSA-75mr-qw9x-3r39
- GO-2026-6360 CVE-2026-73840 GHSA-c5f6-2rm9-2w8g
- GO-2026-6361 CVE-2026-72921 GHSA-gv5w-hfx8-8cwq
- GO-2026-6362 CVE-2026-73843 GHSA-qh9r-j7rp-4x2m
- GO-2026-6363 CVE-2026-67445 GHSA-w878-pj84-3j5v
- GO-2026-6364 GHSA-99rq-75j6-5j9f
- GO-2026-6365 GHSA-gw25-m53r-qh88
- GO-2026-6367 CVE-2026-56743 GHSA-fm8w-2m5w-9j7r
- GO-2026-6368 CVE-2026-75602 GHSA-h6cj-26g5-67fv
- GO-2026-6369 CVE-2026-73232 GHSA-jcvh-xf52-2cwm
- GO-2026-6370 CVE-2026-73292 GHSA-8cj9-r88m-8945
- GO-2026-6371 CVE-2026-73293 GHSA-cxvf-gvfq-36w2
- GO-2026-6373 CVE-2026-69086 GHSA-7hm9-v7vf-7g4w
- GO-2026-6374 CVE-2026-69083 GHSA-fph3-ghq9-vw66
- GO-2026-6377 CVE-2026-69084 GHSA-vh22-h7hf-www7
- GO-2026-6379 CVE-2026-68586 GHSA-36v8-mpjm-8j5r
- GO-2026-6381 CVE-2026-68587 GHSA-69mh-gvh4-8gp7
- GO-2026-6382 CVE-2026-68584 GHSA-7j72-f6wg-cxw6
- GO-2026-6384 CVE-2026-68585 GHSA-pm3w-vxp9-ccwc
- GO-2026-6386 CVE-2026-72809 GHSA-3mp7-4rh5-jrv9
- GO-2026-6387 CVE-2026-72805 GHSA-67x2-mq63-v9vm
- GO-2026-6388 CVE-2026-72806 GHSA-6mcf-g667-w3qv
- GO-2026-6392 CVE-2026-72801 GHSA-8x84-r2ff-h8pq
- GO-2026-6395 CVE-2026-72800 GHSA-5fhr-f75j-8wr9
- GO-2026-6398 CVE-2026-72802 GHSA-jv8v-xq2h-657v
- GO-2026-6400 CVE-2026-72810 GHSA-mw8r-mw84-88v2
- GO-2026-6402 CVE-2026-72811 GHSA-q2vg-7qgx-x5fc
- GO-2026-6404 CVE-2026-72803…
- Record
openSUSE-SU-2026:21897-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:23855-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
Changes for govulncheck-vulndb:
- Update to version 0.0.20260916T180043 2026-09-16T18:00:43Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-6348 CVE-2026-84304 GHSA-vp52-pcj8-j9qc
- GO-2026-6356 CVE-2026-65959 GHSA-mhc4-g3wh-cw7m
- GO-2026-6366 CVE-2026-61625 GHSA-8q3c-rjr9-xxrp
- GO-2026-6372 CVE-2026-79921 GHSA-6c5v-hqjr-5xxp
- GO-2026-6441 CVE-2026-84303 GHSA-qc2q-p7wx-3px3
- GO-2026-6443 CVE-2026-84445 GHSA-2v4p-qf9q-27wj
- GO-2026-6444 CVE-2026-53495 GHSA-7jxh-36q5-gcqv
- GO-2026-6445 CVE-2025-58363 GHSA-c23q-fw86-9h5x
- GO-2026-6446 CVE-2025-24978 GHSA-g8rh-fjm6-h2h9
- GO-2026-6447 CVE-2025-24979 GHSA-pqqc-8v73-9gg2
- GO-2026-6448 CVE-2026-59185 GHSA-cp3j-m783-3ph5
- GO-2026-6449 GHSA-hxjg-93wc-h8p8
- GO-2026-6450 CVE-2026-59172 GHSA-m835-3cm9-rggg
- GO-2026-6451 CVE-2026-59157 GHSA-v25g-mvwr-f5fp
- GO-2026-6452 CVE-2026-59162 GHSA-fx5j-qcqg-grpf
- GO-2026-6453 CVE-2026-59161 GHSA-q5j5-6p94-4gwc
- GO-2026-6454 CVE-2026-88012 GHSA-7ghq-v6jf-g56c
- GO-2026-6455 CVE-2026-88011 GHSA-rf44-j88r-hh8c
- GO-2026-6456 CVE-2026-88045 GHSA-2p48-j3qc-rx9f
- GO-2026-6457 CVE-2026-88046 GHSA-38xv-hf3p-h7mq
- GO-2026-6458 CVE-2026-88017 GHSA-c476-6w5q-jw77
- GO-2026-6459 CVE-2026-88016 GHSA-f8g7-2xjc-7mfh
- GO-2026-6460 CVE-2026-88044 GHSA-p569-5gjg-9cmj
- GO-2026-6461 CVE-2026-88015 GHSA-p6m2-r3w9-mpxw
- GO-2026-6462 CVE-2026-88018 GHSA-xwwr-4h3p-r22c
- GO-2026-6463 CVE-2026-88013 GHSA-486v-q2wf-fp2r
- GO-2026-6464 CVE-2026-88014 GHSA-66hp-wgxq-6f5q
- GO-2026-6465 CVE-2026-88009 GHSA-f52w-8j3h-j724
- GO-2026-6466 CVE-2026-88007 GHSA-qqjf-53cj-pwvv
- GO-2026-6467 CVE-2026-88004 GHSA-v67p-phpq-fc8x
- GO-2026-6468 CVE-2026-88008 GHSA-w4v4-9rw7-5326
- GO-2026-6469 CVE-2026-56665 GHSA-v77h-2w3m-94hx
- GO-2026-6470 CVE-2026-56666 GHSA-992q-9gwp-7r79
- GO-2026-6473 CVE-2026-76081 GHSA-v859-c572-qh5p
- GO-2026-6474 CVE-2026-56668 GHSA-vrh8-c9cm-wh8v
- Update to version 0.0.20260910T144842 2026-09-10T14:48:42Z.
- GO-2026-6302 GHSA-mf7q-r4rv-jv94
- GO-2026-6343 CVE-2026-25782 GHSA-qm72-8prh-g92x
- GO-2026-6344 CVE-2026-26292 GHSA-rc56-rj3f-xggf
- GO-2026-6345 CVE-2026-27779 GHSA-v8f2-2ghq-9whv
- GO-2026-6346 CVE-2026-27780 GHSA-vhq7-fwwh-7hjf
- GO-2026-6347 CVE-2026-27660 GHSA-x92v-f5gc-r34v
- GO-2026-6350 CVE-2026-59832 GHSA-275h-v5h9-vr82
- GO-2026-6351 CVE-2026-72920 GHSA-2v6v-25fm-p4fg
- GO-2026-6353 CVE-2026-59834 GHSA-h89q-4j2h-7h88
- GO-2026-6357 CVE-2026-73667 GHSA-2mw5-23gm-pccq
- GO-2026-6358 CVE-2026-73841 GHSA-52gf-6rpq-fgmx
- GO-2026-6359 CVE-2026-67446 GHSA-75mr-qw9x-3r39
- GO-2026-6360 CVE-2026-73840 GHSA-c5f6-2rm9-2w8g
- GO-2026-6361 CVE-2026-72921 GHSA-gv5w-hfx8-8cwq
- GO-2026-6362 CVE-2026-73843 GHSA-qh9r-j7rp-4x2m
- GO-2026-6363 CVE-2026-67445 GHSA-w878-pj84-3j5v
- GO-2026-6364 GHSA-99rq-75j6-5j9f
- GO-2026-6365 GHSA-gw25-m53r-qh88
- GO-2026-6367 CVE-2026-56743 GHSA-fm8w-2m5w-9j7r
- GO-2026-6368 CVE-2026-75602 GHSA-h6cj-26g5-67fv
- GO-2026-6369 CVE-2026-73232 GHSA-jcvh-xf52-2cwm
- GO-2026-6370 CVE-2026-73292 GHSA-8cj9-r88m-8945
- GO-2026-6371 CVE-2026-73293 GHSA-cxvf-gvfq-36w2
- GO-2026-6373 CVE-2026-69086 GHSA-7hm9-v7vf-7g4w
- GO-2026-6374 CVE-2026-69083 GHSA-fph3-ghq9-vw66
- GO-2026-6377 CVE-2026-69084 GHSA-vh22-h7hf-www7
- GO-2026-6379 CVE-2026-68586 GHSA-36v8-mpjm-8j5r
- GO-2026-6381 CVE-2026-68587 GHSA-69mh-gvh4-8gp7
- GO-2026-6382 CVE-2026-68584 GHSA-7j72-f6wg-cxw6
- GO-2026-6384 CVE-2026-68585 GHSA-pm3w-vxp9-ccwc
- GO-2026-6386 CVE-2026-72809 GHSA-3mp7-4rh5-jrv9
- GO-2026-6387 CVE-2026-72805 GHSA-67x2-mq63-v9vm
- GO-2026-6388 CVE-2026-72806 GHSA-6mcf-g667-w3qv
- GO-2026-6392 CVE-2026-72801 GHSA-8x84-r2ff-h8pq
- GO-2026-6395 CVE-2026-72800 GHSA-5fhr-f75j-8wr9
- GO-2026-6398 CVE-2026-72802 GHSA-jv8v-xq2h-657v
- GO-2026-6400 CVE-2026-72810 GHSA-mw8r-mw84-88v2
- GO-2026-6402 CVE-2026-72811 GHSA-q2vg-7qgx-x5fc
- GO-2026-6404 CVE-2026-72803…
- Record
SUSE-SU-2026:23855-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:23863-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
Changes for govulncheck-vulndb:
- Update to version 0.0.20260916T180043 2026-09-16T18:00:43Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-6348 CVE-2026-84304 GHSA-vp52-pcj8-j9qc
- GO-2026-6356 CVE-2026-65959 GHSA-mhc4-g3wh-cw7m
- GO-2026-6366 CVE-2026-61625 GHSA-8q3c-rjr9-xxrp
- GO-2026-6372 CVE-2026-79921 GHSA-6c5v-hqjr-5xxp
- GO-2026-6441 CVE-2026-84303 GHSA-qc2q-p7wx-3px3
- GO-2026-6443 CVE-2026-84445 GHSA-2v4p-qf9q-27wj
- GO-2026-6444 CVE-2026-53495 GHSA-7jxh-36q5-gcqv
- GO-2026-6445 CVE-2025-58363 GHSA-c23q-fw86-9h5x
- GO-2026-6446 CVE-2025-24978 GHSA-g8rh-fjm6-h2h9
- GO-2026-6447 CVE-2025-24979 GHSA-pqqc-8v73-9gg2
- GO-2026-6448 CVE-2026-59185 GHSA-cp3j-m783-3ph5
- GO-2026-6449 GHSA-hxjg-93wc-h8p8
- GO-2026-6450 CVE-2026-59172 GHSA-m835-3cm9-rggg
- GO-2026-6451 CVE-2026-59157 GHSA-v25g-mvwr-f5fp
- GO-2026-6452 CVE-2026-59162 GHSA-fx5j-qcqg-grpf
- GO-2026-6453 CVE-2026-59161 GHSA-q5j5-6p94-4gwc
- GO-2026-6454 CVE-2026-88012 GHSA-7ghq-v6jf-g56c
- GO-2026-6455 CVE-2026-88011 GHSA-rf44-j88r-hh8c
- GO-2026-6456 CVE-2026-88045 GHSA-2p48-j3qc-rx9f
- GO-2026-6457 CVE-2026-88046 GHSA-38xv-hf3p-h7mq
- GO-2026-6458 CVE-2026-88017 GHSA-c476-6w5q-jw77
- GO-2026-6459 CVE-2026-88016 GHSA-f8g7-2xjc-7mfh
- GO-2026-6460 CVE-2026-88044 GHSA-p569-5gjg-9cmj
- GO-2026-6461 CVE-2026-88015 GHSA-p6m2-r3w9-mpxw
- GO-2026-6462 CVE-2026-88018 GHSA-xwwr-4h3p-r22c
- GO-2026-6463 CVE-2026-88013 GHSA-486v-q2wf-fp2r
- GO-2026-6464 CVE-2026-88014 GHSA-66hp-wgxq-6f5q
- GO-2026-6465 CVE-2026-88009 GHSA-f52w-8j3h-j724
- GO-2026-6466 CVE-2026-88007 GHSA-qqjf-53cj-pwvv
- GO-2026-6467 CVE-2026-88004 GHSA-v67p-phpq-fc8x
- GO-2026-6468 CVE-2026-88008 GHSA-w4v4-9rw7-5326
- GO-2026-6469 CVE-2026-56665 GHSA-v77h-2w3m-94hx
- GO-2026-6470 CVE-2026-56666 GHSA-992q-9gwp-7r79
- GO-2026-6473 CVE-2026-76081 GHSA-v859-c572-qh5p
- GO-2026-6474 CVE-2026-56668 GHSA-vrh8-c9cm-wh8v
- Update to version 0.0.20260910T144842 2026-09-10T14:48:42Z.
- GO-2026-6302 GHSA-mf7q-r4rv-jv94
- GO-2026-6343 CVE-2026-25782 GHSA-qm72-8prh-g92x
- GO-2026-6344 CVE-2026-26292 GHSA-rc56-rj3f-xggf
- GO-2026-6345 CVE-2026-27779 GHSA-v8f2-2ghq-9whv
- GO-2026-6346 CVE-2026-27780 GHSA-vhq7-fwwh-7hjf
- GO-2026-6347 CVE-2026-27660 GHSA-x92v-f5gc-r34v
- GO-2026-6350 CVE-2026-59832 GHSA-275h-v5h9-vr82
- GO-2026-6351 CVE-2026-72920 GHSA-2v6v-25fm-p4fg
- GO-2026-6353 CVE-2026-59834 GHSA-h89q-4j2h-7h88
- GO-2026-6357 CVE-2026-73667 GHSA-2mw5-23gm-pccq
- GO-2026-6358 CVE-2026-73841 GHSA-52gf-6rpq-fgmx
- GO-2026-6359 CVE-2026-67446 GHSA-75mr-qw9x-3r39
- GO-2026-6360 CVE-2026-73840 GHSA-c5f6-2rm9-2w8g
- GO-2026-6361 CVE-2026-72921 GHSA-gv5w-hfx8-8cwq
- GO-2026-6362 CVE-2026-73843 GHSA-qh9r-j7rp-4x2m
- GO-2026-6363 CVE-2026-67445 GHSA-w878-pj84-3j5v
- GO-2026-6364 GHSA-99rq-75j6-5j9f
- GO-2026-6365 GHSA-gw25-m53r-qh88
- GO-2026-6367 CVE-2026-56743 GHSA-fm8w-2m5w-9j7r
- GO-2026-6368 CVE-2026-75602 GHSA-h6cj-26g5-67fv
- GO-2026-6369 CVE-2026-73232 GHSA-jcvh-xf52-2cwm
- GO-2026-6370 CVE-2026-73292 GHSA-8cj9-r88m-8945
- GO-2026-6371 CVE-2026-73293 GHSA-cxvf-gvfq-36w2
- GO-2026-6373 CVE-2026-69086 GHSA-7hm9-v7vf-7g4w
- GO-2026-6374 CVE-2026-69083 GHSA-fph3-ghq9-vw66
- GO-2026-6377 CVE-2026-69084 GHSA-vh22-h7hf-www7
- GO-2026-6379 CVE-2026-68586 GHSA-36v8-mpjm-8j5r
- GO-2026-6381 CVE-2026-68587 GHSA-69mh-gvh4-8gp7
- GO-2026-6382 CVE-2026-68584 GHSA-7j72-f6wg-cxw6
- GO-2026-6384 CVE-2026-68585 GHSA-pm3w-vxp9-ccwc
- GO-2026-6386 CVE-2026-72809 GHSA-3mp7-4rh5-jrv9
- GO-2026-6387 CVE-2026-72805 GHSA-67x2-mq63-v9vm
- GO-2026-6388 CVE-2026-72806 GHSA-6mcf-g667-w3qv
- GO-2026-6392 CVE-2026-72801 GHSA-8x84-r2ff-h8pq
- GO-2026-6395 CVE-2026-72800 GHSA-5fhr-f75j-8wr9
- GO-2026-6398 CVE-2026-72802 GHSA-jv8v-xq2h-657v
- GO-2026-6400 CVE-2026-72810 GHSA-mw8r-mw84-88v2
- GO-2026-6402 CVE-2026-72811 GHSA-q2vg-7qgx-x5fc
- GO-2026-6404 CVE-2026-72803…
- Record
SUSE-SU-2026:23863-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/traefik/traefik/v3Go |
3.0.0 up to 3.7.13 | 3.7.13 |
github.com/traefik/traefik/v2Go |
before 2.11.57 | 2.11.57 |
github.com/traefik/traefikGo |
All versions | None known |
govulncheck-vulndbSUSE:Linux Enterprise Server 16.0 From an advisory covering 91 CVEs |
before 0.0.20260916T180043-160000.1.1 | 0.0.20260916T180043-160000.1.1 |
govulncheck-vulndbSUSE:Linux Enterprise Server for SAP applications 16.0 From an advisory covering 91 CVEs |
before 0.0.20260916T180043-160000.1.1 | 0.0.20260916T180043-160000.1.1 |
traefikopenSUSE:Tumbleweed From an advisory covering 5 CVEs |
before 3.7.13-1.1 | 3.7.13-1.1 |
govulncheck-vulndbopenSUSE:Leap 16.0 From an advisory covering 91 CVEs |
before 0.0.20260916T180043-160000.1.1 | 0.0.20260916T180043-160000.1.1 |
Public exploits
Links only. Every CVE stores no exploit code.
| Source | Link | Date |
|---|---|---|
| PoC in GitHub | Boreas37/CVE-2026-88009-PoC | 2026-10-25 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV, PoC in GitHub |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-88009 is a high vulnerability (CVSS 8.8) in Traefik, published September 10, 2026. Public exploit code exists. EPSS puts the chance of exploitation in the next 30 days at 0.44%, the 38th percentile. Fixed in github.com/traefik/traefik/v3 3.7.13.
References
github.com/traefik/traefik/security/advisories/GHSA-f52w-8j3h-j724
github.com/traefik/traefik/pull/13796
github.com/traefik/traefik/commit/58d1e9ca204526823211e30fd4634101c59d58e9
github.com/traefik/traefik/releases/tag/v2.11.57
github.com/traefik/traefik/releases/tag/v3.7.13
nvd.nist.gov/vuln/detail/CVE-2026-88009
Show 97 moreShow less
github.com/advisories/GHSA-f52w-8j3h-j724
github.com/CVEProject/cvelistV5/tree/main/cves/2026/88xxx/CVE-2026-88009.json
github.com/traefik/traefik
suse.com/support/update/announcement/2026/suse-su-202623855-1
suse.com/security/cve/CVE-2025-24978
suse.com/security/cve/CVE-2025-24979
suse.com/security/cve/CVE-2025-58363
suse.com/security/cve/CVE-2026-11720
suse.com/security/cve/CVE-2026-25782
suse.com/security/cve/CVE-2026-26292
suse.com/security/cve/CVE-2026-27660
suse.com/security/cve/CVE-2026-27779
suse.com/security/cve/CVE-2026-27780
suse.com/security/cve/CVE-2026-53495
suse.com/security/cve/CVE-2026-56665
suse.com/security/cve/CVE-2026-56666
suse.com/security/cve/CVE-2026-56668
suse.com/security/cve/CVE-2026-56743
suse.com/security/cve/CVE-2026-59157
suse.com/security/cve/CVE-2026-59161
suse.com/security/cve/CVE-2026-59162
suse.com/security/cve/CVE-2026-59172
suse.com/security/cve/CVE-2026-59185
suse.com/security/cve/CVE-2026-59832
suse.com/security/cve/CVE-2026-59834
suse.com/security/cve/CVE-2026-60004
suse.com/security/cve/CVE-2026-61625
suse.com/security/cve/CVE-2026-65959
suse.com/security/cve/CVE-2026-67445
suse.com/security/cve/CVE-2026-67446
suse.com/security/cve/CVE-2026-68584
suse.com/security/cve/CVE-2026-68585
suse.com/security/cve/CVE-2026-68586
suse.com/security/cve/CVE-2026-68587
suse.com/security/cve/CVE-2026-69083
suse.com/security/cve/CVE-2026-69084
suse.com/security/cve/CVE-2026-69086
suse.com/security/cve/CVE-2026-71493
suse.com/security/cve/CVE-2026-71494
suse.com/security/cve/CVE-2026-72789
suse.com/security/cve/CVE-2026-72790
suse.com/security/cve/CVE-2026-72792
suse.com/security/cve/CVE-2026-72793
suse.com/security/cve/CVE-2026-72794
suse.com/security/cve/CVE-2026-72795
suse.com/security/cve/CVE-2026-72796
suse.com/security/cve/CVE-2026-72797
suse.com/security/cve/CVE-2026-72798
suse.com/security/cve/CVE-2026-72799
suse.com/security/cve/CVE-2026-72800
suse.com/security/cve/CVE-2026-72801
suse.com/security/cve/CVE-2026-72802
suse.com/security/cve/CVE-2026-72803
suse.com/security/cve/CVE-2026-72804
suse.com/security/cve/CVE-2026-72805
suse.com/security/cve/CVE-2026-72806
suse.com/security/cve/CVE-2026-72807
suse.com/security/cve/CVE-2026-72808
suse.com/security/cve/CVE-2026-72809
suse.com/security/cve/CVE-2026-72810
suse.com/security/cve/CVE-2026-72811
suse.com/security/cve/CVE-2026-72812
suse.com/security/cve/CVE-2026-72920
suse.com/security/cve/CVE-2026-72921
suse.com/security/cve/CVE-2026-73087
suse.com/security/cve/CVE-2026-73232
suse.com/security/cve/CVE-2026-73292
suse.com/security/cve/CVE-2026-73293
suse.com/security/cve/CVE-2026-73294
suse.com/security/cve/CVE-2026-73667
suse.com/security/cve/CVE-2026-73840
suse.com/security/cve/CVE-2026-73841
suse.com/security/cve/CVE-2026-73842
suse.com/security/cve/CVE-2026-73843
suse.com/security/cve/CVE-2026-75602
suse.com/security/cve/CVE-2026-76081
suse.com/security/cve/CVE-2026-79921
suse.com/security/cve/CVE-2026-84303
suse.com/security/cve/CVE-2026-84304
suse.com/security/cve/CVE-2026-84445
suse.com/security/cve/CVE-2026-88004
suse.com/security/cve/CVE-2026-88007
suse.com/security/cve/CVE-2026-88008
suse.com/security/cve/CVE-2026-88009
suse.com/security/cve/CVE-2026-88011
suse.com/security/cve/CVE-2026-88012
suse.com/security/cve/CVE-2026-88013
suse.com/security/cve/CVE-2026-88014
suse.com/security/cve/CVE-2026-88015
suse.com/security/cve/CVE-2026-88016
suse.com/security/cve/CVE-2026-88017
suse.com/security/cve/CVE-2026-88018
suse.com/security/cve/CVE-2026-88044
suse.com/security/cve/CVE-2026-88045
suse.com/security/cve/CVE-2026-88046
suse.com/support/update/announcement/2026/suse-su-202623863-1
suse.com/security/cve/CVE-2026-88010
Left out here: the rest of 5 source descriptions. The JSON record has them.