Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
🔗 CVE IDs covered (6)
📋 Description
CVE-2026-88858 — grafana: Math expressions could crash Grafana CVE-2026-88967 — grafana: Azure Monitor data source could leak its Azure access token CVE-2026-100105 — grafana: Grafana: Information disclosure via legacy schema switch in contact points CVE-2026-103506 — grafana: SSO secrets readable by low-privileged users when an experimental feature is enabled CVE-2026-106475 — grafana: ELASTICSEARCH DATA SOURCE COULD BE USED TO SEND ARBITRARY REQUESTS TO ELASTICSEARCH CVE-2026-107365 — grafana: GOOGLE CLOUD MONITORING DATA SOURCE COULD REACH OTHER CLOUD MONITORING API PATHS
🎯 Affected products5
- Red Hat Hardened Images
- grafana13.2-0:13.2.5-0.1.hum1@aarch64 as a component of Red Hat Hardened Images
- grafana13.2-0:13.2.5-0.1.hum1@s390x as a component of Red Hat Hardened Images
- grafana13.2-0:13.2.5-0.1.hum1@src as a component of Red Hat Hardened Images
- grafana13.2-0:13.2.5-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: Disable server-side expressions in the Grafana configuration: 1. Edit `/etc/grafana/grafana.ini` and set the following configuration under the `[expressions]` block: ```ini [expressions] enabled = false ``` 2. Restart the Grafana service: ```bash systemctl restart grafana-server ``` Caveats: Disabling expressions completely disables server-side math expressions as well as all expression-based alert rules. Warning: Restarting the `grafana-server` service will cause a temporary interruption of service for active sessions. Workaround: Restrict query permissions on configured Azure Monitor data sources exclusively to trusted users, or remove the data source configuration entirely if it is not in active use. 1. Within the Grafana administration interface, open the Azure Monitor data source settings and adjust permissions to limit query access only to trusted administrative roles. 2. If Azure Monitor is no longer needed, remove the data source configuration from Grafana. 3. At the cloud provider level, reduce permissions assigned to the Azure identity or service principal used by Grafana to enforce the principle of least privilege. Caveats: Restricting query access or deleting the data source will prevent non-administrative users from viewing dashboards, panels, or alerts that rely on Azure Monitor metrics. Workaround: Limit Grafana alerting contact-point create/edit permissions to trusted administrators only. Restrict access to the Grafana management UI and Alerting APIs to trusted networks; rotate contact-point secrets if unauthorized edits are suspected. Workaround: Ensure the experimental `kubernetesSsoSettingsApi` feature toggle is disabled. By default, this feature toggle is inactive. If this feature was manually activated, remove `kubernetesSsoSettingsApi` from the `[feature_toggles]` section in the Grafana configuration file (`grafana.ini`) or from the `GF_FEATURE_TOGGLES_ENABLE` environment variable. Apply the configuration by restarting the service: ``` systemctl restart grafana-server ``` Warning: Restarting the `grafana-server` service will result in a temporary interruption of service for connected users. Additionally, if the toggle was previously enabled, immediately rotate all associated SSO client secrets to prevent unauthorized access from potentially exposed credentials. Workaround: Restrict the permissions granted to the credentials used by Grafana to connect to Elasticsearch: 1. Configure Elasticsearch role-based access control to assign the data source account a strictly read-only role constrained to the specific indices required for monitoring. 2. Ensure that write privileges, index creation or management permissions, and cluster-level administrative rights are removed from the configured data source credentials. Caveats: Applying strict read-only access may disrupt workflows if existing dashboards or integrations expect the data source to write data or query unassigned indices. Grafana does not require a service restart for modified Elasticsearch role permissions to take effect, but changes apply immediately on the Elasticsearch backend. 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.
🔗 References (13)
- selfhttps://access.redhat.com/errata/RHSA-2026:99114
- externalhttps://images.redhat.com/
- externalhttps://access.redhat.com/security/cve/CVE-2026-100105
- externalhttps://access.redhat.com/security/updates/classification/
- externalhttps://access.redhat.com/security/cve/CVE-2026-88967
- externalhttps://access.redhat.com/security/cve/CVE-2026-103506
- externalhttps://access.redhat.com/security/cve/CVE-2026-88858
- externalhttps://access.redhat.com/security/cve/CVE-2026-111000
- externalhttps://access.redhat.com/security/cve/CVE-2026-82014
- externalhttps://access.redhat.com/security/cve/CVE-2026-106475
- externalhttps://access.redhat.com/security/cve/CVE-2026-107365
- externalhttps://access.redhat.com/security/cve/CVE-2026-81843
- selfhttps://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_99114.json