Skip to content

🚨 [security] [backend] Update mongoose 6.0.8 → 9.0.1 (major) #460

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
depfu wants to merge 1 commit into from
Closed

🚨 [security] [backend] Update mongoose 6.0.8 → 9.0.1 (major) #460

depfu wants to merge 1 commit into from

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Dec 6, 2025

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ mongoose (6.0.8 → 9.0.1) · Repo · Changelog

Security Advisories 🚨

🚨 Mongoose search injection vulnerability

Mongoose versions prior to 8.9.5, 7.8.4, and 6.13.6 are vulnerable to improper use of the $where operator. This vulnerability arises from the ability of the $where clause to execute arbitrary JavaScript code in MongoDB queries, potentially leading to code injection attacks and unauthorized access or manipulation of database data.

NOTE: this issue exists because of an incomplete fix for CVE-2024-53900.

🚨 Mongoose search injection vulnerability

Mongoose versions prior to 8.9.5, 7.8.4, and 6.13.6 are vulnerable to improper use of the $where operator. This vulnerability arises from the ability of the $where clause to execute arbitrary JavaScript code in MongoDB queries, potentially leading to code injection attacks and unauthorized access or manipulation of database data.

NOTE: this issue exists because of an incomplete fix for CVE-2024-53900.

🚨 Mongoose search injection vulnerability

Mongoose versions prior to 8.8.3, 7.8.3, and 6.13.5 are vulnerable to improper use of the $where operator. This vulnerability arises from the ability of the $where clause to execute arbitrary JavaScript code in MongoDB queries, potentially leading to code injection attacks and unauthorized access or manipulation of database data.

🚨 Mongoose search injection vulnerability

Mongoose versions prior to 8.8.3, 7.8.3, and 6.13.5 are vulnerable to improper use of the $where operator. This vulnerability arises from the ability of the $where clause to execute arbitrary JavaScript code in MongoDB queries, potentially leading to code injection attacks and unauthorized access or manipulation of database data.

🚨 Mongoose search injection vulnerability

Mongoose versions prior to 8.8.3, 7.8.3, and 6.13.5 are vulnerable to improper use of the $where operator. This vulnerability arises from the ability of the $where clause to execute arbitrary JavaScript code in MongoDB queries, potentially leading to code injection attacks and unauthorized access or manipulation of database data.

🚨 Mongoose Prototype Pollution vulnerability

Prototype Pollution in GitHub repository automattic/mongoose prior to 7.3.3, 6.11.3, and 5.13.20.

🚨 Mongoose Prototype Pollution vulnerability

Prototype Pollution in GitHub repository automattic/mongoose prior to 7.3.3, 6.11.3, and 5.13.20.

🚨 Mongoose Vulnerable to Prototype Pollution in Schema Object

Description

Mongoose is a MongoDB object modeling tool designed to work in an asynchronous environment.

Affected versions of this package are vulnerable to Prototype Pollution. The Schema.path() function is vulnerable to prototype pollution when setting the schema object. This vulnerability allows modification of the Object prototype and could be manipulated into a Denial of Service (DoS) attack.

Proof of Concept

// poc.js
const mongoose = require('mongoose');
const schema = new mongoose.Schema();

malicious_payload = 'proto.toString'


schema.path(malicious_payload, [String])


x = {}

console.log(x.toString()) // crashed (Denial of service (DoS) attack)

Impact

This vulnerability can be manipulated to exploit other types of attacks, such as Denial of service (DoS), Remote Code Execution, or Property Injection.

🚨 automattic/mongoose vulnerable to Prototype pollution via Schema.path

Mongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. Affected versions of this package are vulnerable to Prototype Pollution. The Schema.path() function is vulnerable to prototype pollution when setting the schema object. This vulnerability allows modification of the Object prototype and could be manipulated into a Denial of Service (DoS) attack.

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​types/webidl-conversions (indirect, 6.1.1 → 7.0.3) · Repo

Sorry, we couldn't find anything useful about this release.

↗️ @​types/whatwg-url (indirect, 8.2.1 → 13.0.0) · Repo

Sorry, we couldn't find anything useful about this release.

↗️ bson (indirect, 4.5.2 → 7.0.0) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ kareem (indirect, 2.3.2 → 3.0.0) · Repo · Changelog

Release Notes

3.0.0 (from changelog)

  • BREAKING CHANGE: make execPre async and drop callback support #39
  • BREAKING CHANGE: require Node 18
  • feat: overwriteArguments support #42

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ mongodb (indirect, 4.1.1 → 7.0.0) · Repo · Changelog

Security Advisories 🚨

🚨 MongoDB Driver may publish events containing authentication-related data

Some MongoDB Drivers may erroneously publish events containing authentication-related data to a command listener configured by an application. The published events may contain security-sensitive data when specific authentication-related commands are executed.

Without due care, an application may inadvertently expose this sensitive information, e.g., by writing it to a log file. This issue only arises if an application enables the command listener feature (this is not enabled by default).

This issue affects the MongoDB C Driver 1.0.0 prior to 1.17.7, MongoDB PHP Driver 1.0.0 prior to 1.9.2, MongoDB Swift Driver 1.0.0 prior to 1.1.1, MongoDB Node.js Driver 3.6 prior to 3.6.10, MongoDB Node.js Driver 4.0 prior to 4.17.0 and MongoDB Node.js Driver 5.0 prior to 5.8.0. This issue also affects users of the MongoDB C++ Driver dependent on the C driver 1.0.0 prior to 1.17.7 (C++ driver prior to 3.7.0).

🚨 MongoDB Driver may publish events containing authentication-related data

Some MongoDB Drivers may erroneously publish events containing authentication-related data to a command listener configured by an application. The published events may contain security-sensitive data when specific authentication-related commands are executed.

Without due care, an application may inadvertently expose this sensitive information, e.g., by writing it to a log file. This issue only arises if an application enables the command listener feature (this is not enabled by default).

This issue affects the MongoDB C Driver 1.0.0 prior to 1.17.7, MongoDB PHP Driver 1.0.0 prior to 1.9.2, MongoDB Swift Driver 1.0.0 prior to 1.1.1, MongoDB Node.js Driver 3.6 prior to 3.6.10, MongoDB Node.js Driver 4.0 prior to 4.17.0 and MongoDB Node.js Driver 5.0 prior to 5.8.0. This issue also affects users of the MongoDB C++ Driver dependent on the C driver 1.0.0 prior to 1.17.7 (C++ driver prior to 3.7.0).

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ mongodb-connection-string-url (indirect, 2.1.0 → 7.0.0) · Repo · Changelog

Release Notes

7.0.0

7.0.0 (2025-11-05)

The MongoDB Node.js team is pleased to announce version 7.0.0 of the mongodb-connection-string-url package!

Note

There are no major versions 4.x to 6.x of the mongodb-connection-string-url package. The major version of this package has been aligned with the major version of the mongodb package, to make it clearer which versions are intended to be used together.

Release Notes

⚠ Breaking Changes

Minimum supported Node.js version now v20.19.0

The minimum supported Node.js version is now v20.19.0. We strive to keep our minimum supported Node.js version in sync with the runtime's release cadence to keep up with the latest security updates and modern language features. Our TypeScript target has also been updated to ES2023.

All Changes

  • NODE-7058: drop support for Node.js v16 and v18 (#95) (783c85b)

Documentation

3.0.2

3.0.2 (2025-01-14)

The MongoDB Node.js team is pleased to announce version 3.0.2 of the mongodb-connection-string-url package!

Release Notes

This release updates the whatwg-url dependency to either be 13.x or 14.x as either works with this package. Ensuring you have 14 installed in your dependency tree should address the deprecation warning related to 'punycode'

We invite you to try the mongodb-connection-string-url library immediately, and report any issues to the NODE project.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ mpath (indirect, 0.8.4 → 0.9.0) · Repo · Changelog

Release Notes

0.9.0 (from changelog)

  • feat: export stringToParts()

Does any of this look wrong? Please let us know.

↗️ mquery (indirect, 4.0.0 → 6.0.0) · Repo · Changelog

Release Notes

6.0.0 (from changelog)

  • BREAKING CHANGE: Make calling updateOne(), updateMany(), and findOneAndX() with one arg set the query filter rather than the update to line up with modern expectations of optional arguments
  • BREAKING CHANGE: remove debug dependency, use node debuglog instead
  • BREAKING CHANGE: remove count() and findOneAndRemove(): use countDocuments() and findOneAndDelete() instead
  • BREAKING CHANGE: require Node >= 20.19.0
  • feat: add findOneAndDelete, findOneAndReplace, countDocuments, estimatedDocumentCount
  • feat: use mongodb driver 6 in tests

5.0.0 (from changelog)

  • BREAKING CHANGE: drop callback support #137 hasezoey
  • BREAKING CHANGE: remove custom promise library support #137 hasezoey
  • BREAKING CHANGE: remove long deprecated update, remove functions #136 hasezoey
  • BREAKING CHANGE: remove collection ducktyping: first param to mquery() is now always the query filter #138
  • feat: support MongoDB Node driver 5 #137 hasezoey

4.0.3 (from changelog)

  • fix: allow using comment with findOneAndUpdate(), count(), distinct() and hint with findOneAndUpdate() Automattic/mongoose#11793

4.0.2 (from changelog)

  • perf: replace regexp-clone with native functionality #131 Uzlopak

4.0.1 (from changelog)

4.0.0 / 2021-08-24

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ punycode (indirect, 2.1.1 → 2.3.1) · Repo

Commits

See the full diff on Github. The new version differs by 25 commits:

↗️ sift (indirect, 13.5.2 → 17.1.3) · Repo · Changelog

Release Notes

16.0.0 (from changelog)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 72 commits:

↗️ tr46 (indirect, 2.1.0 → 5.1.1) · Repo

Release Notes

5.1.1

Fixes the behavior when useSTD3ASCIIRules is set to true. This regressed in v5.1.0. (#70, @yandrushchak)

5.1.0

Updates to Unicode 16.0.0.

Updates to follow TR 46 revision 33 (spec changelog). This did not include any public API changes but did include some logic changes.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 28 commits:

↗️ webidl-conversions (indirect, 6.1.0 → 7.0.0) · Repo

Commits

See the full diff on Github. The new version differs by 14 commits:

↗️ whatwg-url (indirect, 9.1.0 → 14.2.0) · Repo

Release Notes

14.2.0

Updated our tr46 dependency, which updates our international domain name support to reflect Unicode 16.0.0. Also includes the related changes to the URL Standard:

Added U+005E (^) to the path percent-encode set, per whatwg/url@9bc33c3.

Ensured opaque paths always roundtrip, per whatwg/url@6c78200.

14.1.1

Improved performance for very long inputs.

14.1.0

Added URL.parse(), per whatwg/url@58acb06.

14.0.0

Breaking change: removed Node.js v16 support.

13.0.0

Breaking change: removed Node.js v14 support.

Added URL.canParse(), per whatwg/url@ae3c28b.

Added URLSearchParams's size getter, per whatwg/url@12b6f0c.

Added optional second value argument to URLSearchParams's has() and delete() methods, per whatwg/url@bfb9157.

Changed the serialization of the origin of blob: URLs whose inner URLs were not http: or https: to be "null", per whatwg/url@eee49fd.

12.0.1

Updated our tr46 dependency, which brings along several fixes related to international domain names. Such as:

  • Empty domain name labels, as in https://xn--4-0bd15808a.../, no longer cause URL parsing to fail.
  • Invalid punycode-encoded domain name labels, as in http://xn--ls8h=/, now correctly cause URL parsing to fail.
  • Includes support for Unicode 15.0.0.

As part of this, we are now running against the newly-introduced test data derived from the Unicode Consortium-maintained IdnaTestV2.txt file, and passing them all.

12.0.0

Breaking change: removed Node.js v12 support.

Changed the characters allowed in domains vs. generic hosts, per whatwg/url@35e195a.

Changed the URL API's search and hash setters, as well as the URLSearchParams API, to always ensure the URL is serialize-parse roundtrippable, per whatwg/url@fdaa0e5.

11.0.0

The breaking changes in this release are only to the Low-level URL Standard API. No actual URL parsing or serialization behavior has changed, and users of the URL and URLSearchParams exports are not affected.

These changes follow whatwg/url@fbaa03c.

  • Removed the URL record type's cannotBeABaseURL property.
  • Changed the URL record type's path from always being an array of strings, to being either a single string or an array of strings.
  • Renamed the "cannot-be-a-base-URL path" parser state (i.e. value for stateOverride) to "opaque path".
  • Added the serializePath(urlRecord) export.
  • Added the hasAnOpaquePath(urlRecord) export.

10.0.0

The breaking changes in this release are to the API exported by the whatwg-url/webidl2js-wrapper module. In particular it now is based on webidl2js v17, which changes some of the exported function signatures, and changes the realms of any errors thrown on misuse.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 58 commits:

🆕 @​mongodb-js/saslprep (added, 1.3.2)

🗑️ @​types/node (removed)

🗑️ base64-js (removed)

🗑️ buffer (removed)

🗑️ denque (removed)

🗑️ ieee754 (removed)

🗑️ regexp-clone (removed)

🗑️ saslprep (removed)

🗑️ sliced (removed)

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Dec 6, 2025
@depfu depfu bot mentioned this pull request Dec 6, 2025
Closed
@depfu
Copy link
Contributor Author

depfu bot commented Dec 18, 2025

Closed in favor of #461.

@depfu depfu bot closed this Dec 18, 2025
@depfu depfu bot deleted the depfu/update/backend/npm/mongoose-9.0.1 branch December 18, 2025 20:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

depfu

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant