Skip to content

Require Go 1.26.11: GO-2026-6859 blocks MegaLinter on every pull request #6043

Description

@devantler

🤖 Generated by the Agentic Engineer

Problem

The osv-scanner step in MegaLinter now reports GO-2026-6859 against the Go standard library for modules that declare go 1.26.10. The fix is in 1.26.11. osv-scanner is a blocking linter, and CI - Required Checks requires MegaLinter on pull requests, so every new or re-run pull request is blocked. The merge-group run has no lint job, so PRs already in the queue aren't affected.

Evidence

Acceptance criteria

  • Every module directive pinned to go 1.26.10 requires go 1.26.11. Modules stay tidy, and the root module builds and vets.
  • MegaLinter's osv-scanner passes on the pull request head.

Size

XS

Activity

  1. moved this to 🏃🏻‍♂️ In Progress in 🌊 Project Boardon Nov 11, 2026
  2. devantler commented on Nov 11, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    The new #6042 head also reproduces GO-2026-6859 in the required organization scan (job) and the native gateway fixture scan (job). Both scanners completed and explicitly returned the advisory as blocking.

    The official Go database entry identifies the fixed releases as 1.26.11 and 1.27.4. #6041 now has a native dependency on this issue. I will integrate the reviewed main fix from #6045 before rerunning the Email cleanup delivery checks; the scans and cleanup gate remain enforced.

  3. moved this from 🏃🏻‍♂️ In Progress to ✅ Done in 🌊 Project Boardon Nov 11, 2026
  4. added 3 commits that reference this issue on Nov 11, 2026
  5. devantler commented on Nov 11, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Post-merge verification passed on current main revision 1913f974e5aa5a0e2f72c8bf146e2d7e1104973d: Scan Go Vulnerabilities, run 43106533153, attempt 1, completed successfully at 21:53:36 UTC on 11 November.

    All five jobs completed successfully. The module inventory and its regression checks passed; the root module and both scanned test modules passed their native scan judges. The root scan used Go 1.26.11, analysed 71 packages with Go code and reached no unaccepted advisory. The deliberately vulnerable negative control analysed one package, reported 42 reachable advisories and passed its expected-blocking judge, confirming the scanner was detecting findings.

    The earlier scheduled failure at 8db83359 remains historical evidence. This records the manual scan of the repaired revision; production image rebuilds and their deployment acceptance remain separate.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Fields

    No fields configured for Security.

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions