Skip to content

fix(deps): patch authlib and @clerk/shared Dependabot alerts#8

Closed
Sbussiso wants to merge 1 commit into
masterfrom
claude/zealous-cray-2632e4
Closed

fix(deps): patch authlib and @clerk/shared Dependabot alerts#8
Sbussiso wants to merge 1 commit into
masterfrom
claude/zealous-cray-2632e4

Conversation

@Sbussiso

Copy link
Copy Markdown
Contributor

Summary

Patches the two Dependabot alerts flagged on master:

  • Critical (CVSS 9.1)@clerk/shared 3.47.3 → 3.47.4 via npm overrides on frontend/package.json (GHSA-vqx2-fgx2-5wq9, createRouteMatcher bypass). Transitive via @clerk/clerk-react. Affected paths are @clerk/nextjs/nuxt/astro middleware — we're a React + Vite SPA so the vulnerable code path isn't reachable, but patched since it's a clean drop-in fix.
  • Moderate (CVSS 5.4)authlib 1.6.9 → 1.6.11, pinned as a direct dep in backend/pyproject.toml (GHSA-jj8c-mmj3-mmgv, CSRF in authlib.integrations.*_client.OAuth with cache). Transitive via fastmcp; no direct authlib imports in our code. Follows the existing python-multipart pinning precedent with an inline comment pointing at the advisory.

Both bumps are patch-level (no API changes).

Test plan

  • uv lock regenerated cleanly (authlib 1.6.9 → 1.6.11)
  • npm install regenerated package-lock.json (@clerk/shared 3.47.3 → 3.47.4)
  • Backend: uv run pytest — 201/201 pass
  • Frontend: npm run build — clean
  • CI green on PR
  • Dependabot alerts auto-close on merge to master

🤖 Generated with Claude Code

- backend: pin authlib>=1.6.11 to resolve GHSA-jj8c-mmj3-mmgv (CSRF in
  authlib.integrations.*_client.OAuth with cache). Transitive via
  fastmcp; not reached by our code but patched for defense in depth.
- frontend: override @clerk/shared to ^3.47.4 to resolve
  GHSA-vqx2-fgx2-5wq9 (createRouteMatcher bypass). Transitive via
  @clerk/clerk-react; only affects @clerk/nextjs/nuxt/astro
  middleware, not our Vite SPA, but patched since it is critical.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

Hi @Sbussiso, thanks for taking the time to open this PR.

OpenSentry is source-available under AGPL-3.0 but does not currently accept external code contributions. This PR is being closed automatically — it is not a reflection of the quality of your work.

If you found a bug or have an idea, we would still love to hear about it:

See CONTRIBUTING.md for the full policy.

Thanks for your interest in OpenSentry.

@github-actions github-actions Bot closed this Apr 17, 2026
Sbussiso added a commit that referenced this pull request Apr 26, 2026
Vite 8.0.7's transitive postcss is pinned at 8.5.8, which has an
unpatched moderate XSS via unescaped </style> in CSS stringify output
(GHSA-qx2v-qp2m-jg93 / CVE-2026-41305).  postcss 8.5.10 ships the
escape fix.

Not reachable in our build path — we don't process user-submitted CSS;
postcss only stringifies our own static stylesheets at compile time.
But arguing reachability with the dependency-graph audit is more
effort than the override, so we just take the bump.

Mechanism: ``overrides`` block in package.json forces the resolved
version through every node_modules path.  Mirrors the ``uv constraints``
pattern the backend uses for python-multipart and authlib (see
backend/pyproject.toml's [tool.uv] section) — same goal, same shape,
same comment style.

The ``overridesNotes`` sibling field is for human readers; npm's
overrides validator rejects comment keys inside the overrides block
itself (every key must parse as a valid package name).

Verified locally:
  npm ls postcss            → 8.5.10
  npm audit                 → 0 vulnerabilities
  npm test                  → 29 passed
  npm run build             → clean

Remove the override once Vite's own pin moves past 8.5.10.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@Sbussiso Sbussiso deleted the claude/zealous-cray-2632e4 branch April 26, 2026 06:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant