Repository navigation
Conversation
|
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. |
The github.com/labstack/echo/v4 entries had no upper bound, so every v4 release was reported as affected. Both vulnerabilities were fixed for v4 in commit ebbb855f (labstack/echo#3197) and released in v4.16.3, whose release notes list CVE-2026-118651 and CVE-2026-118653 as fixed. The GHSAs give the v4 range as ">= 4.0.0, <= 4.16.2". Mark v4 as fixed in 4.16.3 and add the v4 fix commit and release references. - data/reports/GO-2026-6872.yaml - data/reports/GO-2026-6875.yaml Fixes golang#6919 Fixes golang#6920 Fixes golang#6922
92f5e34 to
e89e3e0
Compare
|
This PR (HEAD: e89e3e0) has been imported to Gerrit for code review. Please visit Gerrit at https://go-review.googlesource.com/c/vulndb/+/860401. Important tips:
|
|
Message from Gopher Robot: Patch Set 1: (1 comment) Please don’t reply on this GitHub thread. Visit golang.org/cl/860401. |
|
Message from Gopher Robot: Patch Set 1: Congratulations on opening your first change. Thank you for your contribution! Next steps: Most changes in the Go project go through a few rounds of revision. This can be Please don’t reply on this GitHub thread. Visit golang.org/cl/860401. |
|
Message from Anton: Patch Set 1: (1 comment) Please don’t reply on this GitHub thread. Visit golang.org/cl/860401. |
## Description The instrumentation govulncheck job fails on every pull request that changes Go code. The only findings are GO-2026-6872 and GO-2026-6875 in echoserver. echoserver uses echo v4.16.3. The upstream advisories list this version as fixed. The Go vulnerability database still marks every echo v4 release as affected. The database gives no fixed version. When the app is echoserver, the Makefile ignores those two IDs. A different ID in echoserver still fails the job. The same IDs in another app still fail the job. This ignore ends after vuln.go.dev lists v4.16.3 as fixed. ## Motivation The job fails on pull requests that do not change echo. golang/vulndb#6924 updates the database. That pull request is still open. This ignore does not hide a different finding. Fixes #1744
|
Message from BS.홍석준: Patch Set 1: (1 comment) Please don’t reply on this GitHub thread. Visit golang.org/cl/860401. |
|
Message from BS.홍석준: Patch Set 1: (1 comment) Please don’t reply on this GitHub thread. Visit golang.org/cl/860401. |
The github.com/labstack/echo/v4 entries had no upper bound, so every
v4 release was reported as affected. Both vulnerabilities were fixed
for v4 in commit ebbb855f (labstack/echo#3197) and released in
v4.16.3, whose release notes list CVE-2026-118651 and
CVE-2026-118653 as fixed. The GHSAs give the v4 range as
">= 4.0.0, <= 4.16.2". Mark v4 as fixed in 4.16.3 and add the v4
fix commit and release references.
Fixes #6919
Fixes #6920
Fixes #6922