Closed
fix(security): replace mcp/memory with hardened ghcr.io/github/gh-aw-memory#49804
Conversation
…memory image - Add Dockerfile.memory-mcp to build a patched image using node:lts-alpine (fixes CVE-2025-55130 node@22.14.0 and Alpine pkg CVEs) and installing @modelcontextprotocol/server-memory@2026.7.4 (fixes GHSA-w48q-cv73-mx4w sdk@1.0.1 and dependent npm package vulnerabilities) - Add publish-memory-mcp.yml workflow to weekly rebuild/publish ghcr.io/github/gh-aw-memory, parallel to publish-safe-outputs-node.yml - Update server-memory.md to reference ghcr.io/github/gh-aw-memory - Remove stale mcp/memory pin from actions-lock.json and sync derived files - Recompile all workflows so lock files reference ghcr.io/github/gh-aw-memory Closes #49516 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update mcp/memory image to address vulnerabilities
fix(security): replace mcp/memory with hardened ghcr.io/github/gh-aw-memory
Aug 2, 2026
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.
mcp/memory(Docker Hub) has 118 vulnerabilities (8 Critical, 55 High) and hasn't been updated since 2025-05-02. Critical exposures includenode@22.14.0,libcrypto3/libssl3@3.3.3-r0,tar@6.2.1/7.4.3, and@modelcontextprotocol/sdk@1.0.1. Since upstream shows no sign of remediation, this PR moves to an in-house hardened image on GHCR.Changes
actions/setup/js/Dockerfile.memory-mcp— Buildsghcr.io/github/gh-aw-memoryfromnode:lts-alpine(patches Node.js + Alpine OS CVEs via base image +apk upgrade), upgrades npm's bundledtar@^7.5.22andbrace-expansion@^5.0.8, then installs@modelcontextprotocol/server-memory@2026.7.4which pulls in@modelcontextprotocol/sdk@^1.29.0(fixing GHSA-w48q-cv73-mx4w). SetsMEMORY_FILE_PATH=/app/dist/memory.jsonso the existing-v /tmp/gh-aw/cache-memory:/app/distvolume mount continues to work..github/workflows/publish-memory-mcp.yml— Weekly rebuild/publish workflow forghcr.io/github/gh-aw-memory, mirroringpublish-safe-outputs-node.yml. Triggers on upstreamnode:lts-alpinedigest change, Dockerfile change, orserver-memoryversion bump.shared/mcp/server-memory.md—container:updated frommcp/memory→ghcr.io/github/gh-aw-memory.actions-lock.json+ derivedaction_pins.json— Stalemcp/memorypin removed.gh-aw-memorydigest will be populated bygh aw upgradeafter the publish workflow runs for the first time.268
.lock.ymlfiles recompiled to referenceghcr.io/github/gh-aw-memory.