Red Hat Updates PKI, Ignition, kpatch, Grafana, and cjose
Tech GuruQuick Answer
Red Hat published five errata for Dogtag PKI, Ignition, kpatch, Grafana and cjose. Inventory exact components and streams, install the matching signed builds, apply required service or live-kernel procedures, validate identity and monitoring workflows, and retain evidence.
Confirm Scope And Apply The Supported Remediation
What to do now: Inventory RHEL systems using Dogtag PKI, Ignition, kpatch, Grafana or cjose, exact packages and kernels, repositories, exposed services, owners, and maintenance windows. Match each component and host to its individual RHSA; do not treat the grouped package list as applicable to every system or infer identical CVE prerequisites. Install the exact signed builds from the corresponding Red Hat repositories and follow supported service-restart or kpatch activation procedures. Confirm package, service and live-kernel state, test PKI, provisioning, monitoring and token workflows, review failures, and retain repository and change evidence.
Last verified: 2026-10-30 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | RHEL Dogtag PKI, Ignition, kpatch, Grafana, and cjose components on the advisory-listed streams |
|---|---|
| Advisory | RHSA-2026:92408 / RHSA-2026:91719 / RHSA-2026:92629 / RHSA-2026:90811 / RHSA-2026:90812 |
| CVEs | CVE-2026-111943, CVE-2026-33382, CVE-2026-53266, CVE-2026-53938, CVE-2026-68121, CVE-2026-74480, CVE-2026-74582, CVE-2026-80844, CVE-2026-8609, CVE-2026-89058, CVE-2026-89059, CVE-2026-89407 |
| Authoritative release date | 2026-10-29 21:34:04 UTC |
| Authority revision date | 2026-10-30 00:54:11 UTC |
| Affected versions | Advisory-listed packages on Red Hat Enterprise Linux AppStream (v. 10); Red Hat Enterprise Linux AppStream (v. 9); Red Hat Enterprise Linux BaseOS E4S (v.9.2); Red Hat Enterprise Linux CodeReady Linux Builder (v. 9), before the exact fixed builds in the corresponding RHSA. |
| Fixed version | cjose-0:0.6.1-17.el9_8.1.src; dogtag-pki-0:11.9.0-6.el10_2.1.src; grafana-0:10.2.6-23.el9_8.4.src; ignition-0:2.26.0-1.el9_8.2.src; kpatch-patch-5_14_0-284_134_1-0:1-18.el9_2.src; kpatch-patch-5_14_0-284_148_1-0:1-16.el9_2.src; kpatch-patch-5_14_0-284_158_1-0:1-14.el9_2.src; kpatch-patch-5_14_0-284_172_1-0:1-11.el9_2.src; kpatch-patch-5_14_0-284_188_1-0:1-3.el9_2.src |
| CVSS base score | 5.3-8.3 (CVSS v3.1; advisory-specific) |
| CVSS severity | Medium to High |
| Exploitation status | Red Hat does not state that these vulnerabilities are being maliciously exploited.; no exploitation claim is inferred. |
What Changed
Five errata update security and platform-management components for 12 CVEs. Red Hat rates the grouped errata Important, Moderate; individual CVSS scores and prerequisites differ by CVE.
What To Validate Now
- Inventory. Inventory RHEL systems using Dogtag PKI, Ignition, kpatch, Grafana or cjose, exact packages and kernels, repositories, exposed services, owners, and maintenance windows.
- Establish applicability. Match each component and host to its individual RHSA; do not treat the grouped package list as applicable to every system or infer identical CVE prerequisites.
- Remediate. Install the exact signed builds from the corresponding Red Hat repositories and follow supported service-restart or kpatch activation procedures.
- Validate. Confirm package, service and live-kernel state, test PKI, provisioning, monitoring and token workflows, review failures, and retain repository and change evidence.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
PKI and live-kernel changes require recovery planning, while Grafana and Ignition can affect management paths. Stage each component independently and preserve rollback.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
