CVE-2026-83493

OpenShift AI workload repository CI could expose privileged secrets

Red Hat · OpenShift AI · distributed-workloads repository CI

First documented disclosure · Review checkpoint

Summary

A crafted pull request could expose CI secrets and potentially the repository write token.

Severity and exploitation evidence

Medium · numeric CVSS score not recorded. Severity source.

Exploitation not established: The reviewed sources document a weakness or controlled demonstration; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

A pull_request_target workflow processed contributor-controlled code with base-repository secrets and its default write token.

Conditions required

An attacker can submit a pull request to a repository running the vulnerable workflow.

Potential impact

Exposure of SNYK_TOKEN, unauthorized Snyk integration use, and potential repository write authority.

Affected versions and configurations

The red-hat-data-services/distributed-workloads workflow; Red Hat still lists rhoai/odh-training-cuda128-torch29-py312-rhel9 as Affected without a version range.

Fix and mitigation status

Red Hat says the vulnerable workflow was deleted and SNYK_TOKEN removed. This is a repository-level remediation, not a verified released package fix.

Practical next steps

Ensure the vulnerable workflow and exposed secret are removed; audit token use and do not run untrusted pull-request code in a privileged workflow context.

Operating lesson

AI project CI secrets must not be available to untrusted contributor code.

Evidence and limits

Red Hat supplies an August 31 public date and Moderate severity without a numerical CVSS score. Fresh November 22 review found the specific OpenShift AI project scope and explicit workflow-removal statement; it does not establish a customer runtime exploit. The API bug title mentions mutable action references, while its detailed description and remediation identify privileged pull-request execution; the row follows the detailed statement and preserves that metadata inconsistency. Package state remains Affected despite the repository remediation. No separate workflow correction commit was supplied by the reviewed authority sources.

Sources