Skip to content

x/vulndb: suggestion regarding GO-2026-6875Β #6922

Open

Description

@bs-sjhong

Report ID

GO-2026-6872

Suggestion/Comment

The report lists github.com/labstack/echo/v4 as affected from 4.0.0 with no upper bound (the range only has introduced: 4.0.0, no fixed or last_affected), and ecosystem_specific is empty. As a result every v4 release, including v4.16.3, is treated as affected, and govulncheck reports the vulnerability as called with "Fixed in: N/A" for any module that uses echo v4.

The upstream advisory GHSA-99jh-6h7p-pp36 lists the v4 range differently. Via the GitHub API (/advisories/GHSA-99jh-6h7p-pp36), the v4 entry has vulnerable_version_range ">= 4.0.0, <= 4.16.2" and first_patched_version null. So v4.16.3 appears to be outside the affected range, but the report lost the upper bound.

Timeline (UTC):

  • 2026-10-28T19:53:24Z GHSA-99jh-6h7p-pp36 published
  • 2026-10-30T04:31:42Z github.com/labstack/echo/v4 v4.16.3 released
  • 2026-11-05T22:54:32Z GO-2026-6875 published (REVIEWED)

Could you update the v4 range, for example by adding last_affected: 4.16.2 (or fixed: 4.16.3 if the v4 fix is confirmed)? I have not verified which v4 commit contains the fix; the report's FIX reference only points to the v5 commit.

The same issue applies to GO-2026-6872 (GHSA-246p-cpwv-v3jq), which I am reporting separately.

Activity

  1. added a commit that references this issue on Nov 6, 2026
    e89e3e0
  2. gopherbot commented on Nov 6, 2026

    @gopherbot
    Contributor

    Change https://go.dev/cl/860401 mentions this issue: data/reports: update GO-2026-6872, GO-2026-6875

  3. gopherbot commented on Nov 6, 2026

    @gopherbot
    Contributor

    Change https://go.dev/cl/860781 mentions this issue: data/reports: review 15 reports

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions