Remove vulnerable gh-aw-firewall agent 0.27.44 container image pin - #52947
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix container vulnerabilities for ghcr.io/github/gh-aw-firewall/agent:0.27.44
Remove vulnerable gh-aw-firewall agent 0.27.44 container image pin
Aug 15, 2026
pelikhan
marked this pull request as ready for review
August 15, 2026 19:00
Contributor
There was a problem hiding this comment.
Pull request overview
Removes the vulnerable gh-aw-firewall agent 0.27.44 digest from embedded lock metadata.
Changes:
- Removes the vulnerable pin from all synchronized catalogs.
- Adds a patch changeset documenting the remediation.
Show a summary per file
| File | Description |
|---|---|
.github/aw/actions-lock.json |
Removes the source container pin. |
pkg/actionpins/data/action_pins.json |
Updates embedded action-pin data. |
pkg/workflow/data/action_pins.json |
Updates embedded workflow data. |
.changeset/patch-remove-vulnerable-awf-0-27-44-agent-pin.md |
Documents the security fix. |
Review details
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
- Files reviewed: 4/4 changed files
- Comments generated: 1
- Review effort level: Balanced
| "gh-aw": patch | ||
| --- | ||
|
|
||
| Remove vulnerable `ghcr.io/github/gh-aw-firewall/agent:0.27.44` container image pin from shared action lock data. The image digest `sha256:0d727725c737b58c7bdf51f640cffb928385ec46517e0917c7f1a02f1bada8b4` is flagged by daily container scanning for High severity Node.js CVEs (CVE-2026-56846, CVE-2026-56848, CVE-2026-58043) and npm dependency advisories in `brace-expansion` and `ip-address`. The default firewall version is already `v0.28.1`; removing this historical agent pin prevents the vulnerable digest from being resolved from embedded lock metadata. |
Contributor
|
🎉 This pull request is included in a new release. Release: |
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.
Daily container scanning flagged
ghcr.io/github/gh-aw-firewall/agent:0.27.44(digestsha256:0d727725…bada8b4) for High-severity Node.js CVEs (CVE-2026-56846, CVE-2026-56848, CVE-2026-58043) plusbrace-expansionandip-addressadvisories. This was the last remaining 0.27.44 firewall pin — the squid, cli-proxy, and api-proxy pins for the same version were already removed in earlier remediations.Changes
.github/aw/actions-lock.json— dropped theghcr.io/github/gh-aw-firewall/agent:0.27.44container entry:pkg/actionpins/data/action_pins.json,pkg/workflow/data/action_pins.json— regenerated viamake sync-action-pins..changeset/patch-remove-vulnerable-awf-0-27-44-agent-pin.md— patch changeset following the wording of the prior 0.27.44 pin removals.Notes
v0.28.1; its pins are untouched..lock.ymlreferenced the removed digest, so no recompilation is required. Removing the historical entry prevents the vulnerable digest from being resolved from embedded lock metadata.