Daily QAJanuary 22, 2026: NPM Security Vulnerabilities (Recurring) #1892
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-01-29T19:20:34.054Z. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
Detected 8 moderate npm security vulnerabilities in documentation dependencies (3rd occurrence in 4 days). All vulnerabilities stem from mermaid v11.12.2 → lodash-es prototype pollution chain.
Key Findings
Security⚠️
Repository Health ✅
Could Not Verify (Go not in environment)
Actions Taken
npm audit fix --force(mermaid 11.12.2 → 10.9.5)Recurring Pattern
Recommendations
Immediate:
docs/package.jsonmermaid to^10.9.5docs/package-lock.jsonvianpm installLong-term:
~10.9.5to prevent auto-upgradesCommands Used
Vulnerability Details
{ "lodash-es": { "severity": "moderate", "via": [{ "source": 1112453, "title": "Lodash Prototype Pollution in _.unset and _.omit", "url": "https://github.com/advisories/GHSA-xxjr-mmjv-4gpg", "cvss": { "score": 6.5 } }], "range": "4.0.0 - 4.17.22", "fixAvailable": { "name": "mermaid", "version": "10.9.5", "isSemVerMajor": true } } }Permission Errors
Attempted to create PR but encountered:
Daily QA bot needs write permissions to create branches/PRs, or manual intervention required.
Beta Was this translation helpful? Give feedback.
All reactions