Skip to content

Bump lodash, @nestjs/config and @nestjs/swagger#6246

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/multi-c0c646446a
Open

Bump lodash, @nestjs/config and @nestjs/swagger#6246
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/multi-c0c646446a

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot bot commented on behalf of github Apr 16, 2026

Bumps lodash, @nestjs/config and @nestjs/swagger. These dependencies needed to be updated together.
Updates lodash from 4.17.21 to 4.18.1

Release notes

Sourced from lodash's releases.

4.18.1

Bugs

Fixes a ReferenceError issue in lodash lodash-es lodash-amd and lodash.template when using the template and fromPairs functions from the modular builds. See lodash/lodash#6167

These defects were related to how lodash distributions are built from the main branch using https://github.com/lodash-archive/lodash-cli. When internal dependencies change inside lodash functions, equivalent updates need to be made to a mapping in the lodash-cli. (hey, it was ahead of its time once upon a time!). We know this, but we missed it in the last release. It's the kind of thing that passes in CI, but fails bc the build is not the same thing you tested.

There is no diff on main for this, but you can see the diffs for each of the npm packages on their respective branches:

4.18.0

v4.18.0

Full Changelog: lodash/lodash@4.17.23...4.18.0

Security

_.unset / _.omit: Fixed prototype pollution via constructor/prototype path traversal (GHSA-f23m-r3pf-42rh, fe8d32e). Previously, array-wrapped path segments and primitive roots could bypass the existing guards, allowing deletion of properties from built-in prototypes. Now constructor and prototype are blocked unconditionally as non-terminal path keys, matching baseSet. Calls that previously returned true and deleted the property now return false and leave the target untouched.

_.template: Fixed code injection via imports keys (GHSA-r5fr-rjxr-66jc, CVE-2026-4800, 879aaa9). Fixes an incomplete patch for CVE-2021-23337. The variable option was validated against reForbiddenIdentifierChars but importsKeys was left unguarded, allowing code injection via the same Function() constructor sink. imports keys containing forbidden identifier characters now throw "Invalid imports option passed into _.template".

Docs

  • Add security notice for _.template in threat model and API docs (#6099)
  • Document lower > upper behavior in _.random (#6115)
  • Fix quotes in _.compact jsdoc (#6090)

lodash.* modular packages

Diff

We have also regenerated and published a select number of the lodash.* modular packages.

These modular packages had fallen out of sync significantly from the minor/patch updates to lodash. Specifically, we have brought the following packages up to parity w/ the latest lodash release because they have had CVEs on them in the past:

Commits
  • cb0b9b9 release(patch): bump main to 4.18.1 (#6177)
  • 75535f5 chore: prune stale advisory refs (#6170)
  • 62e91bc docs: remove n_ Node.js < 6 REPL note from README (#6165)
  • 59be2de release(minor): bump to 4.18.0 (#6161)
  • af63457 fix: broken tests for _.template 879aaa9
  • 1073a76 fix: linting issues
  • 879aaa9 fix: validate imports keys in _.template
  • fe8d32e fix: block prototype pollution in baseUnset via constructor/prototype traversal
  • 18ba0a3 refactor(fromPairs): use baseAssignValue for consistent assignment (#6153)
  • b819080 ci: add dist sync validation workflow (#6137)
  • Additional commits viewable in compare view

Updates @nestjs/config from 3.3.0 to 4.0.4

Release notes

Sourced from @​nestjs/config's releases.

Release 4.0.4

  • fix(deps): update dependency dotenv to v17.4.1 (6bc5737)
  • fix(deps): update dependency lodash to v4.18.1 [security] (f31ee98)

Release 4.0.3

What's Changed

Full Changelog: nestjs/config@4.0.2...4.0.3

Release 4.0.2

  • fix(common): update KeyOf type to support symbol keys (f53f14e)

Release 4.0.1

  • fix: validate predefined condition #1970 (79d82d6)
  • feat: allow to use symbol as a token (99d8bca)

Release 4.0.0

Breaking changes

The order in which configuration variables are read by the ConfigService#get method has been updated. The new order is:

  • Internal configuration (config namespaces and custom config files)
  • Validated environment variables (if validation is enabled and a schema is provided)
  • The process.env object

Previously, validated environment variables and the process.env object were read first, preventing them from being overridden by internal configuration. With this update, internal configuration will now always take precedence over environment variables.

Additionally, the ignoreEnvVars configuration option, which previously allowed disabling validation of the process.env object, has been deprecated. Instead, use the validatePredefined option (set to false to disable validation of predefined environment variables). Predefined environment variables refer to process.env variables that were set before the module was imported. For example, if you start your application with PORT=3000 node main.js, the PORT variable is considered predefined. However, variables loaded by the ConfigModule from a .env file are not classified as predefined.

A new skipProcessEnv option has also been introduced. This option allows you to prevent the ConfigService#get method from accessing the process.env object entirely, which can be helpful when you want to restrict the service from reading environment variables directly.

Changelog

  • chore: update config attributes to more self descriptive names (c2eaf04)
  • chore(deps): update nest monorepo to v11 (1c20713)
  • feat: order of reading variables, add skip predefined (c53c63c)
Commits
  • 3b5d592 chore(): release v4.0.4
  • 4fbcb03 Merge pull request #2263 from nestjs/renovate/dotenv-17.x
  • 33dae89 Merge pull request #2269 from nestjs/renovate/cimg-node-24.x
  • 0a727c3 Merge pull request #2313 from nestjs/renovate/npm-lodash-vulnerability
  • 6bc5737 fix(deps): update dependency dotenv to v17.4.1
  • f31ee98 fix(deps): update dependency lodash to v4.18.1 [security]
  • 059314c chore(deps): update dependency typescript-eslint to v8.58.1 (#2315)
  • 0f81e2d chore(deps): update dependency eslint to v10.2.0 (#2314)
  • e673ab2 chore(deps): update dependency @​types/node to v24.12.2 (#2311)
  • b1ede30 chore(deps): update nest monorepo to v11.1.18 (#2312)
  • Additional commits viewable in compare view

Updates @nestjs/swagger from 8.1.1 to 11.3.0

Release notes

Sourced from @​nestjs/swagger's releases.

Release 11.3.0

11.3.0 (2026-04-15)

Bug fixes

Enhancements

Dependencies

Committers: 7

11.2.7

What's Changed

... (truncated)

Commits
  • 0106583 chore(): release v11.3.0
  • 473b26f chore: add rxjs as dev dependency
  • 5b0b014 test: regenerate api-spec
  • 410d6a7 Merge pull request #3826 from Nedunchezhiyan-M/fix/api-response-nullable
  • b1e16e6 Merge pull request #3849 from nestjs/renovate/release-it-20.x
  • 71d9f7a chore(deps): update dependency release-it to v20
  • fa96c15 Merge pull request #3625 from rajasekar33/feat/add-api-level-extensions
  • 672a40d Merge pull request #3449 from leemhoon00/feat-apiheader-example
  • b0f01d5 Merge pull request #3784 from maruthang/fix/nullable-type-field-3274
  • 4063d94 Merge pull request #3774 from SupunGeethanjana/issue/3772
  • Additional commits viewable in compare view
Install script changes

This version adds prepare script that runs during installation. Review the package contents before updating.


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [lodash](https://github.com/lodash/lodash), [@nestjs/config](https://github.com/nestjs/config) and [@nestjs/swagger](https://github.com/nestjs/swagger). These dependencies needed to be updated together.

Updates `lodash` from 4.17.21 to 4.18.1
- [Release notes](https://github.com/lodash/lodash/releases)
- [Commits](lodash/lodash@4.17.21...4.18.1)

Updates `@nestjs/config` from 3.3.0 to 4.0.4
- [Release notes](https://github.com/nestjs/config/releases)
- [Commits](nestjs/config@3.3.0...4.0.4)

Updates `@nestjs/swagger` from 8.1.1 to 11.3.0
- [Release notes](https://github.com/nestjs/swagger/releases)
- [Commits](nestjs/swagger@8.1.1...11.3.0)

---
updated-dependencies:
- dependency-name: lodash
  dependency-version: 4.18.1
  dependency-type: direct:production
- dependency-name: "@nestjs/config"
  dependency-version: 4.0.4
  dependency-type: direct:production
- dependency-name: "@nestjs/swagger"
  dependency-version: 11.3.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Apr 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Development

Successfully merging this pull request may close these issues.

0 participants