fix(deps): remediate PROD-5108 security findings - #3964
fix(deps): remediate PROD-5108 security findings#3964plural-copilot[bot] wants to merge 4 commits into
Conversation
There was a problem hiding this comment.
This PR was generated by the codex Plural Agent Runtime. Here's some useful information you might want to know to evaluate the ai's perfomance:
| Name | Details |
|---|---|
| 💬 Prompt | Create one PR against the current default/master branch to remediate Linear issue PROD-5108. The target repository is explicitly pluralsh/console.... |
| 🔗 Run history | View run history |
Soffi AI SummaryThis PR remediates a batch of production security findings (PROD-5108) across the JavaScript, Go, and Elixir dependency stacks in a single, coordinated change set. The motivation is to bring multiple CVE-flagged packages up to patched versions before they can be exploited, while also performing the required React Router v6 → v7 / Sentry v7 compatibility migration that was a prerequisite for the JavaScript (Yarn): Go: Elixir: Proxy / adapter fixes: The Tesla HTTP adapter used in Commits
Updated: 2026-08-04 21:27 UTC |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Greptile SummaryThis dependency-focused PR updates vulnerable JavaScript, Go, and Elixir packages and migrates the frontend’s Sentry integration to React Router 7.
Confidence Score: 4/5The PR appears safe to merge, but the unsupported Req override should be validated against the production reverse-proxy streaming paths or paired with a compatible adapter upgrade. The dependency graph resolves successfully, and no blocking incompatibility was established; the remaining concern is that Req 0.6.3 is forced into reverse_proxy_plug 3.0.2 despite that adapter declaring compatibility only through Req 0.5.x. Files Needing Attention: mix.exs and mix.lock
|
| Filename | Overview |
|---|---|
| assets/package.json | Upgrades React Router and pins remediated transitive JavaScript dependencies. |
| assets/src/App.tsx | Migrates Sentry’s browser-router wrapper from its React Router 6 API to the version 7 API. |
| assets/src/instrument.ts | Migrates Sentry browser tracing to its React Router 7 integration. |
| assets/yarn.lock | Resolves the requested JavaScript dependency upgrades consistently with the manifest. |
| go/controller/go.mod | Updates the indirect cel-go dependency to v0.29.0. |
| go/datastore/go.mod | Updates the indirect cel-go dependency to v0.29.0. |
| go/deployment-operator/go.mod | Updates the indirect cel-go dependency to v0.29.0. |
| go/tools/go.mod | Updates the indirect cel-go dependency to v0.29.0. |
| mix.exs | Upgrades Req to 0.6.x but overrides live dependencies whose declared compatibility ranges stop at Req 0.5.x. |
| mix.lock | Resolves the Elixir security upgrades while retaining dependency metadata that documents the unsupported Req version combination. |
Reviews (1): Last reviewed commit: "fix(deps): remediate PROD-5108 security ..." | Re-trigger Greptile
| # if using the Mint adapter: | ||
| {:castore, "~> 1.0", override: true}, | ||
| {:req, "~> 0.5.15", override: true}, | ||
| {:req, "~> 0.6.1", override: true}, |
There was a problem hiding this comment.
Req override exceeds adapter support
The override resolves Req 0.6.3 while the production ReverseProxyPlug.HTTPClient.Adapters.Req dependency declares compatibility only through Req 0.5.x. This leaves the Prometheus and Elasticsearch streaming proxy paths outside the adapter’s supported dependency range, so dependency resolution cannot protect those routes from runtime API or behavior incompatibilities.
Summary
5667ac34592db1c4170819b8b4888012bf488d78), which was based on the same current master commit, then reconciled all lock/module changes through the current Yarn, Go, and Mix tooling rather than copying stale lockfile entries.Fixes PROD-5108
Resolved versions
react-router-dom7.18.0 and resolvedreact-router7.18.0;undici7.29.0;ip-address10.2.2;brace-expansion2.1.4 and 5.0.9 on the affected branches;tar7.5.21;postcss8.5.23.github.com/google/cel-gov0.29.0 ingo/tools,go/deployment-operator,go/datastore, andgo/controller.req0.6.3;gun2.5.0;cowlib2.19.0.CVE coverage
undici7.29.0: CVE-2026-15157, CVE-2026-16729, CVE-2026-14643, CVE-2026-13697, CVE-2026-16728.ip-address10.2.2: CVE-2026-69198, CVE-2026-54272.brace-expansion2.1.4 / 5.0.9: CVE-2026-14257, CVE-2026-69152.tar7.5.21: GHSA-r292-9mhp-454m.react-router7.18.0: CVE-2026-53669, CVE-2026-53666.react-router-dom7.18.0: CVE-2026-53668.github.com/google/cel-gov0.29.0: GHSA-gcjh-h69q-9w9g.postcss8.5.23: CVE-2026-69153.req0.6.3: CVE-2026-49756, CVE-2026-49755.gun2.5.0 /cowlib2.19.0: CVE-2026-43966.Residual alert
hackneyremains 1.25.0, so CVE-2026-47069, CVE-2026-47076, CVE-2026-47075, and CVE-2026-47071 remain. Hex currently offers 4.7.2 as the newer release, but Console directly constrains Hackney to~> 1.21and uses:hackney.stop_async/1plus Hackney pool configuration. Updating to 4.x is a major API/dependency migration and was not forced merely to suppress the alert; it needs dedicated compatibility work.Validation
go get,go mod tidy, andgo mod tidy -diffin each requested module.mix deps.update req gun cowlib hackneyto regeneratemix.lock.git diff --check.