Skip to content

fix(deps): resolve CVE-2025-54798 arbitrary file write in tmp#1002

Merged
sarayev merged 1 commit intomainfrom
fix/dependabot-tmp
Mar 6, 2026
Merged

fix(deps): resolve CVE-2025-54798 arbitrary file write in tmp#1002
sarayev merged 1 commit intomainfrom
fix/dependabot-tmp

Conversation

@sarayev
Copy link
Contributor

@sarayev sarayev commented Mar 6, 2026

Summary

Resolves CVE-2025-54798 (arbitrary file write) in tmp 0.2.1 → 0.2.5.

Changes

  • Added yarn resolution: "tmp": "^0.2.4" — resolves to 0.2.5

Strategy

Traced via yarn why: lerna@5.6.2@nrwl/devkit@15.9.7tmp; lerna@5.6.2nx@15.9.7tmp. Both specify ~0.2.1. lerna@5.6.2 is the final 5.x release — resolution required to force upgrade.

Verification

  • lerna run build
  • lerna run test
  • yarn extract-dependency-licenses ✅ (1 ins/1 del)
  • Cloud E2E: 30/30 passed ✅

…rary file write)

Dependency trace:
- lerna@5.6.2 → @nrwl/devkit@15.9.7 → tmp@~0.2.1 (resolved to 0.2.1)
- lerna@5.6.2 → nx@15.9.7 → tmp@~0.2.1 (resolved to 0.2.1)

Direct parent analysis:
- lerna@5.6.2 is the latest and final release in the 5.x line.
- @nrwl/devkit and nx 15.9.7 both specify tmp@~0.2.1, which DOES accept
  tmp@0.2.4+ (the fixed version), but the lockfile had resolved to 0.2.1
  (the latest at the time the lockfile was created).
- No bump of lerna within its major resolves this since 5.6.2 is already latest.

Resolution 'tmp': '^0.2.4' forces all instances to 0.2.5 (latest 0.2.x),
fixing the CVE. The ~0.2.1 range in both @nrwl/devkit and nx accepts this.
@sarayev sarayev requested review from a team as code owners March 6, 2026 15:41
@sarayev sarayev merged commit 9d45c76 into main Mar 6, 2026
4 checks passed
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.

2 participants