Remove vulnerable gh-aw-firewall/squid:0.27.44 digest pin from shared container pin catalogs - #52829
Merged
pelikhan merged 2 commits intoAug 15, 2026
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix vulnerabilities in container image ghcr.io/github/gh-aw-firewall/squid
Remove vulnerable Aug 15, 2026
gh-aw-firewall/squid:0.27.44 digest pin from shared container pin catalogs
pelikhan
marked this pull request as ready for review
August 15, 2026 05:00
pelikhan
deleted the
copilot/container-image-scan-fix-vulnerabilities-again
branch
August 15, 2026 05:00
Contributor
|
🎉 Great work! This PR successfully addresses a security vulnerability in the pinned squid container image (gh-aw-firewall/squid:0.27.44). The PR is well-focused and properly documented:
This is exactly the kind of security-driven infrastructure maintenance the project needs. Looks ready to go!
|
Contributor
There was a problem hiding this comment.
Pull request overview
Removes the vulnerable AWF Squid 0.27.44 digest from shared pin catalogs and documents the security change.
Changes:
- Removes the affected digest from all three pin catalogs.
- Retains Squid 0.28.1.
- Adds a patch changeset.
Show a summary per file
| File | Description |
|---|---|
.github/aw/actions-lock.json |
Removes the vulnerable canonical pin. |
pkg/actionpins/data/action_pins.json |
Removes the embedded actionpins copy. |
pkg/workflow/data/action_pins.json |
Removes the embedded workflow copy. |
.changeset/patch-remove-vulnerable-awf-0-27-44-squid-pin.md |
Documents the remediation. |
Review details
- Files reviewed: 4/4 changed files
- Comments generated: 1
- Review effort level: Balanced
| "gh-aw": patch | ||
| --- | ||
|
|
||
| Remove vulnerable `ghcr.io/github/gh-aw-firewall/squid:0.27.44` container image pin from shared action lock data. The image digest `sha256:83e48bbe12c634be8c228a576832fe45f66c529ac3659db92bddbcf2eeb6d627` is flagged by daily container scanning for High/Medium CVEs in Alpine packages. The default firewall version is already `v0.28.1`; removing this historical squid 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 image scanning flagged the pinned
ghcr.io/github/gh-aw-firewall/squid:0.27.44@sha256:83e48...image for multiple High/Medium CVEs. This change removes that vulnerable historical squid pin from shared lock metadata so it can no longer be resolved by embedded pin catalogs.Scope of change
ghcr.io/github/gh-aw-firewall/squid:0.27.44container entry from:.github/aw/actions-lock.jsonpkg/actionpins/data/action_pins.jsonpkg/workflow/data/action_pins.json0.28.1squid pin intact.Release note
.changeset/patch-remove-vulnerable-awf-0-27-44-squid-pin.mdPin delta (illustrative)