[Snyk] Fix for 3 vulnerabilities

[0-sayed]

Snyk has created this PR to fix 3 vulnerabilities in the pnpm dependencies of this project.

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue
	Missing Release of Resource after Effective Lifetime SNYK-JS-MULTER-15365916
	Incomplete Cleanup SNYK-JS-MULTER-15365918
	Incorrect Authorization SNYK-JS-NESTJSCORE-15365922

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• Snyk has automatically assigned this pull request, set who gets assigned.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
👩‍💻 Set who automatically gets assigned
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Incorrect Authorization

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request aims to enhance the security posture of the project by upgrading key NestJS dependencies to resolve identified high-severity vulnerabilities. The changes primarily involve updating package versions to incorporate the necessary security patches, ensuring the application benefits from the latest fixes.

Highlights

• Vulnerability Fixes: This pull request addresses three high-severity vulnerabilities: 'Missing Release of Resource after Effective Lifetime' (SNYK-JS-MULTER-15365916), 'Incomplete Cleanup' (SNYK-JS-MULTER-15365918), and 'Incorrect Authorization' (SNYK-JS-NESTJSCORE-15365922).
• Dependency Updates: The @nestjs/core package has been updated from version 11.1.13 to 11.1.14, and @nestjs/platform-express has been updated from 11.1.13 to 11.1.15.
• Manual Intervention Required: The pnpm-lock.yaml file failed to update automatically and requires manual intervention before merging this pull request.

Changelog

• package.json
  • Updated @nestjs/core dependency to ^11.1.14
  • Updated @nestjs/platform-express dependency to ^11.1.15

Activity

• Snyk automatically created this pull request to fix 3 vulnerabilities in the project's pnpm dependencies.
• Snyk reported that the pnpm-lock.yaml file failed to update and needs manual attention.
• Snyk provided links to detailed vulnerability reports and remediation strategies.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates @nestjs/core and @nestjs/platform-express to fix three security vulnerabilities. However, a critical issue exists: the pnpm-lock.yaml file has not been updated. This will prevent the new package versions from being installed, leaving the vulnerabilities unresolved. Please run pnpm install to update the lock file and commit the changes to ensure the fixes are applied.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[gemini-code-assist]

The pnpm-lock.yaml file has not been updated to reflect the version changes in package.json. As noted in the pull request description, this is a critical oversight because the old, vulnerable package versions will still be used during installation. To resolve this and apply the security fixes, please run pnpm install and commit the updated pnpm-lock.yaml file.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 625adb4d19

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Update lockfile after dependency version bumps

This change bumps @nestjs/core and @nestjs/platform-express in package.json but does not update pnpm-lock.yaml, which still pins 11.1.13; in this repo, CI runs pnpm install --frozen-lockfile in .github/workflows/ci.yml (for example lines 63 and 112), and pnpm install --help states --frozen-lockfile will "fail if an update is needed," so the workflow will fail and the vulnerable locked versions remain in use until the lockfile is regenerated and committed.

Useful? React with 👍 / 👎.

[greptile-apps]

Confidence Score: 1/5

• Not safe to merge — the lockfile was not updated, so the three high-severity vulnerabilities remain exploitable post-merge.
• The package.json changes are correct, but pnpm's deterministic install model means only the lockfile matters at install time. pnpm-lock.yaml still resolves both patched packages to the vulnerable 11.1.13, making the security fix entirely ineffective without a lockfile update.
• pnpm-lock.yaml must be regenerated and committed before this PR provides any security value.

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant CI as CI/CD Pipeline
    participant pnpm as pnpm install
    participant Lock as pnpm-lock.yaml
    participant pkg as package.json

    Dev->>CI: Merge PR (package.json bumped)
    CI->>pnpm: Run pnpm install
    pnpm->>Lock: Read locked versions
    Lock-->>pnpm: @nestjs/core@11.1.13 (vulnerable)
    Lock-->>pnpm: @nestjs/platform-express@11.1.13 (vulnerable)
    Note over pnpm: package.json ranges are ignored<br/>lockfile takes precedence
    pnpm-->>CI: Installs vulnerable versions ❌

    Note over Dev,Lock: Required fix: update pnpm-lock.yaml first

    Dev->>pnpm: pnpm update @nestjs/core @nestjs/platform-express
    pnpm->>Lock: Write new pinned versions
    Lock-->>pnpm: @nestjs/core@11.1.14 ✅
    Lock-->>pnpm: @nestjs/platform-express@11.1.15 ✅
    pnpm-->>CI: Installs patched versions ✅

Loading

_{Last reviewed commit: 625adb4}

[greptile-apps]

Lockfile not updated — security fixes won't take effect

The pnpm-lock.yaml was NOT updated as part of this PR. pnpm uses the lockfile for deterministic, reproducible installs. Because pnpm-lock.yaml still pins both packages to 11.1.13:

'@nestjs/core@11.1.13': ...
'@nestjs/platform-express@11.1.13': ...

Running pnpm install (or any CI/CD install step) will continue to resolve and install the vulnerable versions, completely bypassing the package.json bumps introduced here. The three high-severity vulnerabilities (SNYK-JS-MULTER-15365916, SNYK-JS-MULTER-15365918, SNYK-JS-NESTJSCORE-15365922) will therefore not be remediated until the lockfile is regenerated.

Before merging, run:

pnpm update @nestjs/core @nestjs/platform-express

and commit the updated pnpm-lock.yaml.

Prompt To Fix With AI

This is a comment left during a code review.
Path: package.json
Line: 72-75

Comment:
**Lockfile not updated — security fixes won't take effect**

The `pnpm-lock.yaml` was NOT updated as part of this PR. pnpm uses the lockfile for deterministic, reproducible installs. Because `pnpm-lock.yaml` still pins both packages to `11.1.13`:

```
'@nestjs/core@11.1.13': ...
'@nestjs/platform-express@11.1.13': ...
```

Running `pnpm install` (or any CI/CD install step) will continue to resolve and install the **vulnerable** versions, completely bypassing the `package.json` bumps introduced here. The three high-severity vulnerabilities (`SNYK-JS-MULTER-15365916`, `SNYK-JS-MULTER-15365918`, `SNYK-JS-NESTJSCORE-15365922`) will therefore **not** be remediated until the lockfile is regenerated.

Before merging, run:
```
pnpm update @nestjs/core @nestjs/platform-express
```
and commit the updated `pnpm-lock.yaml`.

How can I resolve this? If you propose a fix, please make it concise.