data/reports: update 5 Traefik reports to v3-only modules

[rtribotte]

• data/reports/GO-2025-4205.yaml
• data/reports/GO-2026-4484.yaml
• data/reports/GO-2026-4880.yaml
• data/reports/GO-2026-5083.yaml
• data/reports/GO-2026-5128.yaml

These five reports list github.com/traefik/traefik and
github.com/traefik/traefik/v2 with no versions block, which marks every
v1 and v2 version affected with no fixed version. All five
vulnerabilities are in code that exists only in v3, so users on the
current v2 LTS (v2.11.54) match permanently and no upgrade clears the
finding. The upstream GitHub advisories scope to
github.com/traefik/traefik/v3 only.

GO-2025-4205 (CVE-2025-66491) and GO-2026-5128 (CVE-2026-54762) are in
the Kubernetes ingress-nginx provider, which was added in v3.5.0. The
directory does not exist in v2:

git ls-tree -d --name-only v2.11.54 \
    pkg/provider/kubernetes/ingress-nginx

GO-2026-4880 (CVE-2026-32695) is in the Knative provider, which is
likewise absent from v2 (pkg/provider/kubernetes/knative).

GO-2026-4484 (CVE-2026-25949) is in the TCP STARTTLS handling for
Postgres; pkg/server/router/tcp/postgres.go does not exist in v2.

GO-2026-5083 (CVE-2026-54761) needs more than a file check, since v2
does ship a Kubernetes Gateway provider. The vulnerability is that the
crossProviderNamespaces allowlist was checked against
backendRef.Namespace rather than the route's own namespace, for
HTTPRoute rules with several (WRR) backendRefs. In v2.11.54, in
pkg/provider/kubernetes/gateway/kubernetes.go, neither precondition
holds: internal services are rejected outright in a WRR, and the
allowlist is checked against the route namespace. This is a claim about
that specific defect, not a general statement about the v2 provider.

GO-2026-4679 (CVE-2026-29777) carries the same v1 and v2 module entries
but is not included here; its module list is still under review and
will be corrected in a follow-up.

data/osv was regenerated with vulnreport osv. review_status is left at
UNREVIEWED on all five reports.

Updates #4205
Updates #4484
Updates #4880
Updates #5083
Updates #5128

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gopherbot]

This PR (HEAD: 2696fef) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/vulndb/+/810900.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Gopher Robot:

Patch Set 1:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/810900.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Gopher Robot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
A maintainer will review your change and provide feedback. See
https://go.dev/doc/contribute#review for more info and tips to get your
patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/810900.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: c9ae2f4) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/vulndb/+/810900.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.