Repository navigation
Conversation
|
Security reassessment — 20 November 2026. Fresh Trivy 0.70.0 data (updated 2026-11-19T19:04:59.970326968Z) now classifies CVE-2026-97054 / GO-2026-6859 as high. This is a pre-existing residual, not a newly introduced dependency: both the configured 13.0.2 image and this 13.0.13 candidate contain affected Go versions. For this unchanged candidate digest
The official Go advisory fixes the affected Decision remains neutral; no automatic merge or release. Keep this valid draft open and retain its other security improvements. Next step: use an official supported Grafana image containing patched Go binaries, verify both architectures, and complete the existing independent stateful/staging/backup-and-rollback review. No suppression, exception, alert dismissal or protection change was applied. Assessed PR head: |
Why
The observability stack pins Grafana OSS 13.0.2. Grafana Labs identifies 13.0.13 as a fixed 13.0.x release for CVE-2026-111024, CVE-2026-102589 and CVE-2026-106472, and it is newer than the 13.0.10 fix for CVE-2026-111000. Prometheus is provisioned in source. This does not establish live reachability or a production incident.
Change
Use
grafana/grafana:13.0.13in the owning Compose file and regenerate the observability stack. Grafana's Docker documentation identifiesgrafana/grafanaas the maintained location for the same OSS edition; Docker Hub lists this version for amd64 and arm64. Volume, network, provisioning and deployment settings are unchanged. The generated diff can reorder entries; the parsed configuration changes only the Grafana image.Validation and hold
./stackctl.sh syncreports pre-existing legacy generator drift on the base and on this candidate../stackctl.sh up --dry-run --no-logswas blocked locally because Docker is unavailable. Do not treat the generator replay as a pass for those checks.