fix: fix 19 CVEs#967
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c2545b6f39
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "overrides": { | ||
| "node-forge": "1.3.2", | ||
| "node-forge": "1.4.0", | ||
| "path-to-regexp": "0.1.13", |
There was a problem hiding this comment.
Avoid forcing path-to-regexp 0.1.x on all dependents
This global override/resolution pins every path-to-regexp consumer to 0.1.13, and the lockfile now shows packages that requested newer APIs (e.g., serve-handler requested 3.3.0) being resolved to 0.1.13 instead. That is an API downgrade across major versions: downstream code that uses pathToRegExp.compile(...) in the 1.x/3.x API surface can throw at runtime once those code paths are hit (rewrites/URL generation). The override should be scoped to the vulnerable edge package(s) instead of replacing all majors globally.
Useful? React with 👍 / 👎.
| module github.com/semaphoreio/semaphore/public-api-gateway | ||
|
|
||
| go 1.22 | ||
| go 1.24.0 |
There was a problem hiding this comment.
Align Go module version with container build toolchain
Raising this module to go 1.24.0 without updating the service’s Docker build baseline (the Dockerfile still defaults to Go 1.22 for this app) makes containerized builds depend on automatic remote toolchain download. In restricted CI or network-limited environments, that upgrade path fails before compilation, so builds that previously used the pinned local toolchain can now break. Update the Docker Go version (and similar services changed in this commit) to match the new go.mod requirement.
Useful? React with 👍 / 👎.
CVE-2026-33186 (grpc, CRITICAL) CVE-2026-33891 (node-forge, HIGH) CVE-2026-33894 (node-forge, HIGH) CVE-2026-33895 (node-forge, HIGH) CVE-2026-33896 (node-forge, HIGH) CVE-2026-4867 (path-to-regexp, HIGH) CVE-2026-33671 (picomatch, HIGH) CVE-2026-33195 (activestorage, HIGH) CVE-2025-68121 (stdlib, CRITICAL)
CVE-2026-4800 (lodash, HIGH) CVE-2026-26996 (minimatch, HIGH) CVE-2026-27903 (minimatch, HIGH) CVE-2026-27904 (minimatch, HIGH) CVE-2026-34785 (rack, HIGH) CVE-2026-34829 (rack, HIGH) CVE-2025-15467 (alpine, CRITICAL) OS-EOL-001 (alpine 3.20.3 end of life)
92bf3a2 to
bfe3cee
Compare
CVE-2026-33186 (grpc, CRITICAL)
CVE-2025-15467 (alpine, CRITICAL)
CVE-2026-33891 (node-forge, HIGH)
CVE-2026-33894 (node-forge, HIGH)
CVE-2026-33895 (node-forge, HIGH)
CVE-2026-33896 (node-forge, HIGH)
CVE-2026-4867 (path-to-regexp, HIGH)
CVE-2026-33671 (picomatch, HIGH)
CVE-2026-33195 (activestorage, HIGH)
CVE-2026-4800 (lodash, HIGH)
CVE-2026-26996 (minimatch, HIGH)
CVE-2026-27903 (minimatch, HIGH)
CVE-2026-27904 (minimatch, HIGH)
CVE-2026-34785 (rack, HIGH)
CVE-2026-34829 (rack, HIGH)
OS-EOL-001 (alpine 3.20.3 end of life)
📝 Description
✅ Checklist
This change requires documentation update