Repository navigation
fix(deps): remediate all open critical dependabot advisories - #883
Conversation
GHSA-82r6-8w77-94w6 (anyio < 4.14.2, TLS certificate spoofing) is fixed by relocking to 4.16.0 in e2e/python and both Python SDK packages; the transitive typing-extensions floor moves to 4.16.0 as anyio requires. GHSA-9v8h-qqgm-4m35 (brotli < 1.2.1, out-of-bounds write) is fixed by relocking e2e/tests to 1.2.1. Co-Authored-By: Claude Code <noreply@anthropic.com>
Address GHSA-f3w6-w445-fwh9 / CVE-2026-122006 by moving the three Rails e2e apps from 7.2.3.2 to 8.0.5.2, the first patched release; no 7.2 backport exists. Regenerate each Gemfile.lock with Ruby 3.3.4 / Bundler 2.5.11 and update the demo-rails70 docs to match. Co-Authored-By: Claude Code <noreply@anthropic.com>
Bump root yarn resolutions to patched releases: - next ^15.5.27 -> ^15.5.28 (resolves 15.5.29), fixing GHSA-2464-fhr4-w9xw (RCE via Image Optimization). The 16.x resolutions already resolve to 16.4.3, which is above the patched 16.4.1. - react-server-dom-webpack ^19.2.8 -> ^19.2.9 (resolves 19.3.1), fixing GHSA-xqc2-xf4c-x3h3. - handlebars ^4.7.9 -> ^4.7.10, fixing GHSA-p8wg-vrv2-v86f and GHSA-8r5x-fm3f-whwj. - shell-quote ^1.9.0 -> ^1.11.0 (resolves 1.12.0), fixing GHSA-pqg4-j6r4-53mv, in both yarn.lock and the e2e/react-native npm lock. - piscina ^4.9.3 -> ^4.9.4, fixing GHSA-67c8-pqhq-4rmx without jumping to the incompatible 5.x line. Co-Authored-By: Claude Code <noreply@anthropic.com>
GHSA-82r6-8w77-94w6 (anyio < 4.14.2): the lock introduced with the rebased pip group still resolved 4.9.0. Relock to 4.16.0 (typing-extensions floor moves to 4.16.0). Co-Authored-By: Claude Code <noreply@anthropic.com>
☂️ Python Coverage
Overall Coverage
New FilesNo new covered files... Modified FilesNo covered modified files...
|
zack-winchell-ld
left a comment
There was a problem hiding this comment.
@vadim-korolik should this PR also bump the SDK version? Do we require standalone version bump PRs?
|
No version bump needed here. Nothing under a published artifact changes: the diff is lockfiles and manifest pin ranges ( |
Lockfiles already remediated by main's #757 (python/poetry locks, npm package.json + package-lock, yarn.lock) taken from origin/main; kept this branch's Rails 8.0.5.2 e2e upgrade for the activestorage advisory, which main does not cover. Co-Authored-By: Claude Code <noreply@anthropic.com>
|
Merged Resolution: for every file both sides touched ( The PR is not redundant: main does not touch Two things for @vadim-korolik to decide:
|
Summary
Remediates every open critical Dependabot alert in this repository: 15 alerts covering 9 unique advisories across npm, pip and RubyGems. All changes are dependency and lockfile updates; no SDK source code changes.
Alerts addressed (open critical alerts as of this PR):
< 4.14.2e2e/python,e2e/python-plugin-flask,sdk/@launchdarkly/observability-python,sdk/highlight-py(poetry.lock)< 8.0.5.2e2e/ruby/rails/demo,api-only,demo-rails70(Gemfile,Gemfile.lock)>= 19.2.0, < 19.2.9yarn.lock>= 10.0.0, <= 15.5.27yarn.lock>= 1.0.3, < 1.2.1e2e/tests(poetry.lock)>= 3.0.0, <= 4.7.9yarn.lock>= 4.0.0, <= 4.7.9yarn.lock>= 1.8.4, < 1.11.0yarn.lock,e2e/react-native/package-lock.json< 4.9.4yarn.lockWhat changed
package.jsonresolutions +yarn.lock,e2e/react-nativeoverrides/lock):next15.5.27 -> 15.5.29,react-server-dom-webpack19.2.8 -> 19.3.1,handlebars4.7.9 -> 4.7.10,shell-quote1.10.0 -> 1.12.0,piscina4.9.3 -> 4.9.4.poetry.lock):anyio4.9.0 -> 4.16.0 in all four locks, and thetyping-extensionsfloor moved to 4.16.0;brotli1.2.0 -> 1.2.1 ine2e/tests.Gemfile+ regeneratedGemfile.lock): all three e2e Rails apps move from the Rails 7.2 line torails ~> 8.0.5.2. 8.0.5.2 is the first release patched for the activestorage advisory and there is no 7.2 backport,so the e2e apps cannot stay on 7.2 and remain clean.
demo-rails70's existingjson ~> 2.19.9pin is retained(Rails 8 still cannot use json 3.x). Its README is updated to explain that it no longer exercises the Rails 7 line.
Demo
This is a dependency/lockfile-only change, so the demo is the verification output rather than a recording.
Notes
e2e/nextjsfails to build withCannot find module '../../app/(route-group-test)/[slug]/page.js'. This is pre-existing and unrelated: it reproduces unchanged on Next 15.5.27, and no CI workflow builds that example.🤖 Generated with Claude Code
Opened from termag
Note
Overview
All three Ruby Rails e2e fixtures (
demo,api-only,demo-rails70) move from the 7.2 line torails ~> 8.0.5.2with regeneratedGemfile.lockfiles. 8.0.5.2 is documented as the first release that fixes the critical Active Storage arbitrary file write/read advisory (GHSA-f3w6-w445-fwh9 / CVE-2026-122006); there is no 7.2 backport, so staying on 7.2 would keep Dependabot alerts open.demo-rails70keeps its existingminitest ~> 5.0andjson ~> 2.19.9pins; only the Rails constraint and comments change. Its README is updated to note the app now runs Rails 8 while still usingconfig.load_defaults 7.0, and that it no longer provides Rails 7.0 regression coverage (CI job name unchanged).Lockfile churn includes the full Rails 8 stack (e.g.
activestorage8.0.5.2), plus transitive updates such asrails-html-sanitizer1.7.2,minitest6.x where unpinned (api-only), and newuridependency fromactivesupport8.Reviewed by Cursor Bugbot for commit bad4fd1. Bugbot is set up for automated code reviews on this repo. Configure here.