chore(deps): update dependency lodash to v4.17.23 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
lodash (source)	4.17.21 → 4.17.23

---

Lodash has Prototype Pollution Vulnerability in _.unset and _.omit functions

CVE-2025-13465 / GHSA-xxjr-mmjv-4gpg

More information

Details

Impact

Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the _.unset and _.omit functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes.

The issue permits deletion of properties but does not allow overwriting their original behavior.

Patches

This issue is patched on 4.17.23.

Severity

• CVSS Score: 6.9 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:H/SI:H/SA:H/E:P

References

• https://github.com/lodash/lodash/security/advisories/GHSA-xxjr-mmjv-4gpg
• https://nvd.nist.gov/vuln/detail/CVE-2025-13465
• https://github.com/lodash/lodash/commit/edadd452146f7e4bad4ea684e955708931d84d81
• https://github.com/lodash/lodash

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

lodash/lodash (lodash)

v4.17.23

Compare Source

---

Configuration

📅 Schedule: Branch creation - "" in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Oops! Looks like you forgot to update the changelog. When updating CHANGELOG.md, please consider the following:

• Changelog is read by country implementors who might not always be familiar with all technical details of OpenCRVS. Keep language high-level, user friendly and avoid technical references to internals.
• Answer "What's new?", "Why was the change made?" and "Why should I care?" for each change.
• If it's a breaking change, include a migration guide answering "What do I need to do to upgrade?".

[github-actions]

ℹ️ Coverage metrics explained:
• Statements — Executed code statements (basic logic lines)
• Branches — Tested decision paths (if/else, switch, ternaries)
• Functions — Functions invoked during tests
• Lines — Source lines executed

[github-actions]

📊 commons test coverage

Statements: 67.37%
Branches:   33.29%
Functions:  50.6%
Lines:      66.79%
Updated at: Thu, 22 Jan 2026 10:11:59 GMT

[github-actions]

📊 events test coverage

Statements: 85.31%
Branches:   84.14%
Functions:  90.47%
Lines:      85.31%
Updated at: Thu, 22 Jan 2026 10:16:28 GMT