Skip to content

fix(security): upgrade next-auth 4.24.14 → 4.24.15 (GHSA-7rqj-j65f-68wh) - #4858

Open
kilo-code-bot[bot] wants to merge 1 commit into
mainfrom
security-remediation/next-auth-ghsa-7rqj-j65f-68wh/d58a3b587a-1
Open

fix(security): upgrade next-auth 4.24.14 → 4.24.15 (GHSA-7rqj-j65f-68wh)#4858
kilo-code-bot[bot] wants to merge 1 commit into
mainfrom
security-remediation/next-auth-ghsa-7rqj-j65f-68wh/d58a3b587a-1

Conversation

@kilo-code-bot

@kilo-code-bot kilo-code-bot Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Security Remediation

Upgrades next-auth from 4.24.14 to 4.24.15 to address GHSA-7rqj-j65f-68wh — email normalizer validates the address before Unicode normalization, allowing a homoglyph @ bypass.

Severity: Critical (per advisory)
Exploitable in this codebase: No — the vulnerable built-in EmailProvider code path is not used; authentication uses a custom CredentialsProvider flow.
Risk: Minimal — patch version bump with no breaking changes.

Changes

  • apps/web/package.json: next-auth 4.24.14 → 4.24.15
  • apps/storybook/package.json: next-auth 4.24.14 → 4.24.15
  • pnpm-lock.yaml: updated accordingly

Kilo Security Finding

https://app.kilo.ai/security-agent/findings?findingId=d58a3b58-7a6d-4801-85af-30e05b014d46

Patch bump to address email normalizer homoglyph bypass vulnerability.
The vulnerable code path is not reachable in this codebase (custom
CredentialsProvider flow), but upgrading eliminates the alert.
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.

0 participants