Tier: C — Restricted Pending Review
Risk-Scoring Breakdown
Finding
.github/dependabot.yml only configures gomod, npm, and pip ecosystems across /, /docs, /actions/setup/js, and .github/workflows. It has no docker ecosystem entries for the container images referenced by open container-image-scan issues (ghcr.io/github/gh-aw-firewall/agent, /squid, /api-proxy, /cli-proxy, ghcr.io/github/gh-aw-mcpg, ghcr.io/github/github-mcp-server). As a result, known CVEs (libc6 CVE-2026-5450 per issue #48405; Go runtime GO-2026-4337 per issue #47821) are detected only by periodic manual/scheduled scans and have no automated dependency-bump PR path for remediation, leaving exposure without a structural recovery capability.
Remediation Action
Add package-ecosystem: docker entries to .github/dependabot.yml for each Dockerfile directory backing the gh-aw-firewall/* and gh-aw-mcpg images, with a weekly schedule matching existing ecosystems, so base-image/library CVEs (e.g. libc6, Go runtime) generate automated update PRs instead of relying solely on manual triage of container-image-scan issues.
SLA Urgency
Critical
Discussion Report
See the full UK AI Open Code Risk & Resilience governance discussion report created in this run (Recent-Change Governance Review, 2026-07-30) for the full asset graph, tier classification, and control verification tables. This finding complements — and does not duplicate — the CVE-specific issues #48405 and #47821, which track the individual vulnerabilities rather than the missing automated update-path control.
Generated by UK AI Operational Resilience · auto · 56.3 AIC · ⌖ 8.04 AIC · ⊞ 8.8K · ◷
Tier: C — Restricted Pending Review
Risk-Scoring Breakdown
Finding
.github/dependabot.ymlonly configuresgomod,npm, andpipecosystems across/,/docs,/actions/setup/js, and.github/workflows. It has nodockerecosystem entries for the container images referenced by open container-image-scan issues (ghcr.io/github/gh-aw-firewall/agent,/squid,/api-proxy,/cli-proxy,ghcr.io/github/gh-aw-mcpg,ghcr.io/github/github-mcp-server). As a result, known CVEs (libc6 CVE-2026-5450 per issue #48405; Go runtime GO-2026-4337 per issue #47821) are detected only by periodic manual/scheduled scans and have no automated dependency-bump PR path for remediation, leaving exposure without a structural recovery capability.Remediation Action
Add
package-ecosystem: dockerentries to.github/dependabot.ymlfor each Dockerfile directory backing thegh-aw-firewall/*andgh-aw-mcpgimages, with a weekly schedule matching existing ecosystems, so base-image/library CVEs (e.g. libc6, Go runtime) generate automated update PRs instead of relying solely on manual triage of container-image-scan issues.SLA Urgency
Critical
Discussion Report
See the full UK AI Open Code Risk & Resilience governance discussion report created in this run (Recent-Change Governance Review, 2026-07-30) for the full asset graph, tier classification, and control verification tables. This finding complements — and does not duplicate — the CVE-specific issues #48405 and #47821, which track the individual vulnerabilities rather than the missing automated update-path control.