Skip to content

fix(observability): update Grafana OSS to 13.0.13 - #674

Draft
wax911 wants to merge 1 commit into
devfrom
security/grafana-13.0.13
Draft

wax911 wants to merge 1 commit into
devfrom
security/grafana-13.0.13

Conversation

@wax911

@wax911 wax911 commented Nov 15, 2026

Copy link
Copy Markdown
Member

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.13 in the owning Compose file and regenerate the observability stack. Grafana's Docker documentation identifies grafana/grafana as 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

  • The project's checksum-verified stackctl v0.4.0 produced repeatable output; the three stack structures matched the committed base before editing and differed only in the Grafana image after editing.
  • ./stackctl.sh sync reports pre-existing legacy generator drift on the base and on this candidate. ./stackctl.sh up --dry-run --no-logs was blocked locally because Docker is unavailable. Do not treat the generator replay as a pass for those checks.
  • Keep this a draft pending trusted CI, a full image audit, independent review and a staged health/datasource check with the persisted data volume. A stateful rollout needs an operator-reviewed backup and rollback plan; this draft does not authorize promotion, deployment or data restoration.

wax911 commented Nov 20, 2026

Copy link
Copy Markdown
Member Author

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 sha256:9b031995a5483a44f80a5dd214a70cecb31448b42d765b44d3756e17b855775f, read-only ARM64 and AMD64 scans identify:

  • Grafana server: Go 1.26.10.
  • Bundled Elasticsearch plugin: Go 1.27.3.

The official Go advisory fixes the affected net/http behavior in 1.26.11 / 1.27.4. The relevant HTTP/1 handler configuration and deployed reachability have not been verified; binary version matches do not establish that the vulnerable path is exercised.

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: d7b80bf392ab1fd25ca22b95a934cf2df3c63fec; base: e80a48a8b8d7d4d9732840b618e73a2f4b58a1c3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant