Document blocker for gh-aw-firewall/agent scan remediation

[Copilot]

ghcr.io/github/gh-aw-firewall/agent:0.27.44 is currently flagged with high-severity Node CVEs, but there is no newer upstream AWF release/tag or rebuilt digest available to consume from gh-aw. This PR captures that remediation is upstream-blocked rather than applying a no-op pin churn.

• Problem context

  • Daily container scan reports 3 High Node.js CVEs on the pinned AWF agent image (0.27.44@sha256:0d7277…), plus lower-severity Ubuntu package findings.

• Change scope in this PR

  • No version or digest updates were made to AWF image pins.
  • Existing pin sources remain unchanged (pkg/actionpins/data/action_pins.json, .github/aw/actions-lock.json, and DefaultFirewallVersion).

• Reason for no pin bump

  • Latest available upstream github/gh-aw-firewall release/tag is still v0.27.44.
  • Registry digest for agent:0.27.44 remains unchanged, so any in-repo edit would not remediate the reported CVEs.

• Planned follow-up once upstream publishes patched image

  • Bump DefaultFirewallVersion.
  • Refresh embedded AWF container digests.
  • Recompile lock artifacts to propagate the new pinned references.

"ghcr.io/github/gh-aw-firewall/agent:0.27.44": {
  "image": "ghcr.io/github/gh-aw-firewall/agent:0.27.44",
  "digest": "sha256:0d727725c737b58c7bdf51f640cffb928385ec46517e0917c7f1a02f1bada8b4"
}

• Fixes [container-image-scan] Container findings for gh-aw-firewall/agent #51967

[github-actions]

Thanks for creating this blocker documentation! 🎯 This PR clearly captures an upstream-blocked remediation scenario for the gh-aw-firewall agent container image CVEs.

A couple of things to get this ready:

• Add implementation — This is currently a draft with no file changes. Consider adding comments or documentation in the relevant files so future maintainers understand why the pinned version remains unchanged.
• Verify scope — Once committed, make sure any documentation files reference the linked issue for visibility.

The description is excellent — it sets clear expectations for the follow-up work once upstream publishes a patched image. Once the implementation is in place, this should be good to go.

Generated by ✅ Contribution Check · auto · 57.9 AIC · ⌖ 3.64 AIC · ⊞ 8.8K · ◷