[Aikido] Fix security issue in i18next via major version upgrade from 23.4.6 to 24.1.2 in with-crossmint#35
Merged
yosriady merged 3 commits intoJun 16, 2026
Conversation
|
Dependency limit exceeded — report not shown. This pull request scan exceeded the 10,000-dependency limit applied to this scan, so the results are incomplete and may be inaccurate. To avoid reporting false positives, Socket has not posted a report. Upgrade your plan to raise the dependency limit and get complete reports, or view the partial scan in the dashboard. Socket is always free for open source. If this is a non-commercial open source project, contact us to request a free Team account. |
Forces the patched shell-quote (>=1.8.4) for the GHSA-w7jw-789q-3m8p critical advisory, pulled in transitively via @crossmint/client-sdk-react-ui. Resolves the failing critical-gated pnpm audit for with-crossmint.
…ith-angular Completes the Dependabot @angular/common 21.2.13->21.2.17 bump (PR #34), which failed CI because it bumped @angular/common alone: @angular/core and the other framework packages stayed on 21.2.13, leaving the high-severity advisories unresolved and creating a peer-dependency mismatch (@angular/common@21.2.17 requires @angular/core@21.2.17). - Bump all @angular/* framework packages (common, compiler, core, forms, platform-browser, router, compiler-cli) to ^21.2.17 in lockstep. This clears the high advisories GHSA-rgjc-h3x7-9mwg, GHSA-39pv-4j6c-2g6v, GHSA-48r7-hpm6-gfxm, GHSA-p3vc-36g9-x9gr and GHSA-q6f4-qqrg-jv6x, all of which are only patched in >=21.2.17. - Exempt the @angular framework packages from the 7-day minimumReleaseAge gate: 21.2.17 is the sole patched release and is still inside the window, so the gate would otherwise block the fix. - Force ws>=8.21.0 via overrides to clear GHSA-96hv-2xvq-fx4p (memory exhaustion DoS) pulled in transitively through viem, the remaining high that kept the with-angular audit red. @angular/build and @angular/cli stay at 21.2.11 (no 21.2.17 exists; their ^21.0.0 peer ranges accept the bumped framework). Verified: pnpm audit --prod --audit-level=high reports no vulnerabilities, frozen-lockfile install is consistent, and ng build succeeds.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrade i18next to fix code injection vulnerability in translation function that could allow arbitrary code execution through prototype pollution attacks.
All breaking changes by upgrading i18next from version 23.4.6 to 24.1.2 (CHANGELOG)
initImmediatetoinitAsync✅ 1 CVE resolved by this upgrade
This PR will resolve the following CVEs:
i18n.tfunction allows attackers to access JavaScript objects likeconstructorwhen requested keys don't exist, potentially enabling arbitrary code execution.Need help on this PR? Tag
/codesmithwith what you need. Autofix is disabled.