fix: bump lodash to 4.17.23 to fix CVE-2025-13465

[evervault-dependencies]

Linear: COM-211

CVE-2025-13465 — Lodash prototype pollution in _.unset / _.omit

• Severity: MEDIUM | CVSS: 6.5
• SLA Deadline: 2026-05-29T18:11:52.722Z
• Affected: lodash >=4.0.0, <=4.17.22
• Fixed in: lodash 4.17.23
• Dependabot Alert: https://github.com/evervault/evervault-node/security/dependabot/68

Summary

Lodash >=4.0.0, <=4.17.22 is vulnerable to prototype pollution via the _.unset and _.omit helpers. Attacker-controlled paths can be crafted so Lodash walks into the prototype chain and deletes methods from built-in prototypes (e.g. Object.prototype.hasOwnProperty). The flaw only allows deleting properties, not overwriting them, but downstream code that relies on those methods can break or be coerced down a different path.

Exposure in evervault-node

• lodash is not a direct dependency. It is pulled in transitively only by nock@12.0.3 (a devDependency).
• No file under lib/, types/, tests/, or e2e/ imports lodash.
• The published artefact ships only lib and types, so lodash is never delivered to SDK consumers.
• Production attack surface is effectively zero; this fix is hygiene to clear the Dependabot alert before the SLA deadline.

Remediation

Added a scoped npm overrides entry pinning vulnerable lodash to the fixed line:

"overrides": {
  "js-yaml": "4.1.1",
  "lodash@>=4.0.0 <4.17.23": "^4.17.23"
}

The key scopes the override to vulnerable versions within the same major line; the caret on the value allows the resolver to select the best compatible patched version without jumping major.

Verification

• npm ls lodash resolves the transitive lodash via nock@12.0.3 to a non-vulnerable version (>=4.17.23 within the 4.x line).
• npm test results match the master baseline; no regressions introduced by this change.
• nock@12.0.3 declares lodash: ^4.17.13, so the override stays within its semver range — no nock upgrade required.

References

• GHSA: GHSA-xxjr-mmjv-4gpg
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-13465
• Fix commit: lodash/lodash@edadd45
• Advisory: GHSA-xxjr-mmjv-4gpg
• Dependabot alert: https://github.com/evervault/evervault-node/security/dependabot/68

[changeset-bot]

⚠️ No Changeset found

Latest commit: 08a9f17

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	uuid@​8.1.0 ⏵ 8.3.2	+1		+1
	sinon@​9.0.2 ⏵ 9.2.4
	husky@​7.0.2 ⏵ 7.0.4
	chai-as-promised@​7.1.1 ⏵ 7.1.2
	sinon-chai@​3.5.0 ⏵ 3.7.0
	nyc@​17.0.0 ⏵ 17.1.0	+1
	axios@​1.12.2 ⏵ 1.16.1	-12	+50
	chai@​4.4.1 ⏵ 4.5.0	+12
	asn1js@​3.0.5 ⏵ 3.0.10	+1		+1
	typescript@​5.3.3 ⏵ 5.9.3
	msgpackr@​1.10.1 ⏵ 1.11.12	+1		+1	+2
	@​changesets/​cli@​2.29.7 ⏵ 2.31.0			+1
	lint-staged@​11.1.2 ⏵ 11.2.6	+1		+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		License policy violation: npm caniuse-lite under CC-BY-4.0 License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (npm metadata) License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/package.json) License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/LICENSE) From: package-lock.json → npm/nyc@17.1.0 → npm/caniuse-lite@1.0.30001793 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001793. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm chai-as-promised under WTFPL License: WTFPL - The applicable license policy does not permit this license (5) (npm metadata) License: WTFPL - The applicable license policy does not permit this license (5) (package/LICENSE.txt) License: WTFPL - The applicable license policy does not permit this license (5) (package/package.json) From: package-lock.json → npm/chai-as-promised@7.1.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/chai-as-promised@7.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm typescript under CC-BY-4.0 License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/ThirdPartyNoticeText.txt) License: MIT-Khronos-old - The applicable license policy does not permit this license (5) (package/ThirdPartyNoticeText.txt) License: LicenseRef-W3C-Community-Final-Specification-Agreement - The applicable license policy does not permit this license (5) (package/ThirdPartyNoticeText.txt) From: package-lock.json → npm/typescript@5.9.3 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@5.9.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report