Red Hat rhc-worker-playbook Update Fixes Five RHEL 10 Flaws

P1 — VALIDATE AND UPDATEHigh · 7.5 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

RHSA-2026:70103 updates rhc-worker-playbook to 0.2.3-6.el10_0.1 for RHEL 10.0 EUS. The package is a yggdrasil worker that receives Ansible playbooks and executes them on the local host; coordinate its update with the system-management owner.

Confirm Scope And Apply The Supported Fix

What to do now: Locate managed hosts with the worker installed, confirm the RHEL 10.0 EUS repository, and schedule the package update around pending management jobs.

Open the authoritative advisory

Source check: 2026-10-02 UTC. This notice reflects the primary-source evidence described below, not a completed update or exploitation test. Recheck the advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeRHEL 10.0 EUS rhc-worker-playbook packages
AdvisoryRHSA-2026:70103
CVEsCVE-2026-33818, CVE-2026-56853, CVE-2026-56859, CVE-2026-56860, CVE-2026-56862
Authoritative release dateRHSA-2026:70103: 2026-09-22T11:06:36+00:00 (CSAF initial release)
Authority revision dateRHSA-2026:70103: 2026-09-22T11:06:36+00:00 (CSAF revision history). CSAF generation timestamps are not advisory revision dates.
Affected versionsThe exact entitled RHEL 10.0 EUS rhc-worker-playbook packages builds before the branch-specific package, image, or digest listed by Red Hat.
Fixed versionrhc-worker-playbook 0.2.3-6.el10_0.1
CVSS base score7.5 (CVSS v3.1)
CVSS severityHigh
Exploitation statusRHSA-2026:70103 does not state that these flaws are being exploited. That is not confirmation that exploitation has not occurred.

What Changed

The five CVEs concern excessive work or resource consumption in Go ASN.1, XML, URL, HTTP/2 and TLS handling. The published vectors describe denial of service, not a demonstrated arbitrary-playbook or remote-code-execution bypass.

What To Validate Now

  1. Inventory. Record worker RPM versions, support repository, yggdrasil connectivity, pending playbook jobs and the accountable automation owner.
  2. Establish applicability. Compare each deployment with the authority's affected-version statement: The exact entitled RHEL 10.0 EUS rhc-worker-playbook packages builds before the branch-specific package, image, or digest listed by Red Hat. Do not infer applicability from product family or severity alone.
  3. Remediate. Apply rhc-worker-playbook 0.2.3-6.el10_0.1 through the supported vendor or project channel, following the current advisory and change-control requirements.
  4. Validate. Check the full installed RPM release, worker/service health and management connectivity, then run an approved low-impact representative playbook and confirm its reported result. Record failed or pending jobs.
  5. 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

Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.

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.