Repository navigation
fix(security): patch Noema reader transitive vulnerabilities - #2629
Merged
Merged
Conversation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
…erabilities-20261013
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Noema document reader lock still contained two fixable vulnerabilities: HIGH CVE-2026-104850 in @modelcontextprotocol/sdk 1.30.0 and CRITICAL CVE-2026-90711 in proxy-addr 2.0.7. Pin SDK 1.31.0 and proxy-addr 2.0.8 as source overrides and regenerate the existing npm lock using Node 22.23.3 with scripts disabled. hwp-mcp 0.3.0 and @rhwp/core 0.7.7 stay pinned.
Validation: npm ci --ignore-scripts --omit=dev completed, npm ls resolved exactly one overridden SDK and proxy-addr, the reader modules imported on Node 22.23.3, focused Python checks passed 17 with 2 existing fixture skips, and refreshed-DB Trivy found zero fixable HIGH/CRITICAL findings in this exact tree. No security exceptions or gate changes.
Summary by CodeRabbit