RHSA-2026:100117MediumCVSS 5.5

Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update

Published
November 13, 2026
Last Modified
November 17, 2026

🔗 CVE IDs covered (2)

📋 Description

CVE-2026-107365 — grafana: GOOGLE CLOUD MONITORING DATA SOURCE COULD REACH OTHER CLOUD MONITORING API PATHS CVE-2026-110289 — grafana: GIT SYNC CONNECTIONS COULD SEND CREDENTIALS TO INTERNAL ADDRESSES

🎯 Affected products5

  • Red Hat Hardened Images
  • grafana13.1-0:13.1.10-0.1.hum1@aarch64 as a component of Red Hat Hardened Images
  • grafana13.1-0:13.1.10-0.1.hum1@s390x as a component of Red Hat Hardened Images
  • grafana13.1-0:13.1.10-0.1.hum1@src as a component of Red Hat Hardened Images
  • grafana13.1-0:13.1.10-0.1.hum1@x86_64 as a component of Red Hat Hardened Images

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Workaround: To mitigate this vulnerability, enforce least-privilege access controls and disable credential forwarding on the Google Cloud Monitoring data source: 1. Configure the data source with service account credentials restricted strictly to read-only Cloud Monitoring roles on explicitly designated Google Cloud projects. 2. Ensure that "Forward OAuth Identity" and "Workload Identity Federation" settings are disabled on the affected data source. 3. If Google Cloud Monitoring is not required, remove the data source from Grafana or restrict data source query permissions to administrative users. Warning: If data sources are provisioned via configuration files on the host, applying changes may require restarting the service (`systemctl restart grafana-server`), which will cause a brief interruption of service. Restricting credentials will prevent users from accessing metrics outside designated projects. Workaround: Audit existing Git Sync and OAuth connector configurations within the Grafana administrative interface to verify that all connection URLs point exclusively to trusted, external repositories rather than loopback or internal network destinations. Additionally, enforce egress network filtering on the host or container network to restrict outbound traffic from the Grafana process to internal subnets and local loopback addresses, allowing connections only to verified Git server hosts. Caveat: Restricting outbound network traffic may disrupt legitimate connections to internal data sources, alert endpoints, or local authentication providers if network filtering rules are overly restrictive.

🔗 References (12)