Skip to content

Bump next 15.1.6 -> 15.5.18 in frontend/nextjs#31

Merged
Gabrielpanga merged 1 commit into
masterfrom
chore/frontend-nextjs-bump-next
May 13, 2026
Merged

Bump next 15.1.6 -> 15.5.18 in frontend/nextjs#31
Gabrielpanga merged 1 commit into
masterfrom
chore/frontend-nextjs-bump-next

Conversation

@Gabrielpanga
Copy link
Copy Markdown
Member

Summary

Same-major bump of next in frontend/nextjs to clear the critical and one high advisory.

Before

  • 4 vulnerabilities (1 critical, 1 high, 2 moderate)
    • Critical: Information exposure in Next.js dev server due to lack of origin verification
    • High: Next.JS DoS via cache poisoning
    • 2 transitive moderate advisories

After

  • 4 vulnerabilities (0 critical, 1 high, 3 moderate)
    • 1 high remaining: jsonwebtoken via pluggy-sdk 0.31.1 — needs a major pluggy-sdk bump (separate PR)
    • 3 moderate (next/postcss, pluggy-sdk/jsonwebtoken transitive)

Net: criticals cleared. The remaining high is gated on a major migration tracked elsewhere.

Change

- "next": "15.1.6"
+ "next": "15.5.18"

Same-major (15.x), non-breaking per Next.js release notes.

Test plan

  • npm ci succeeds in frontend/nextjs
  • npm run build succeeds
  • npm run dev boots and the demo connect token flow works

Clears the critical and one high advisory:
- Information exposure in Next.js dev server due to lack of origin
  verification (CRITICAL)
- Next.JS DoS via cache poisoning (HIGH)

Remaining 1 high (jsonwebtoken via pluggy-sdk 0.31.1) requires a
major pluggy-sdk bump and is tracked separately.

Same-major, non-breaking.
@Gabrielpanga Gabrielpanga requested a review from a team as a code owner May 11, 2026 12:36
@Gabrielpanga Gabrielpanga merged commit 39cb747 into master May 13, 2026
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