CVE-2026-71459

Description

JobJobEventsChildrenSummary view has no model/parent_model. ModelAccessPermission.check_get_permissions() falls through (returns True) for any authenticated user. The view uses raw get_object_or_404(Job, pk) without DRF object-level permission check. Zero-privilege user reads event tree structure, event_processing_finished status, and enumerates Job IDs platform-wide via 200/404 oracle. Sibling endpoint /jobs/{id}/job_events/ correctly returns 403.

Statement

A moderate information-disclosure access-control flaw was found in the automation-controller component of Red Hat Ansible Automation Platform. The JobJobEventsChildrenSummary API view does not declare model or parent_model attributes, so ModelAccessPermission.check_get_permissions() falls through and returns True for any authenticated user, and the view fetches the requested Job directly without an object-level permission check. An authenticated attacker holding any valid credential, even one with no assigned privileges, can therefore read the job event tree structure and event_processing_finished status of arbitrary jobs belonging to any organization, and can enumerate valid job IDs platform-wide via the 200/404 response oracle, bypassing the role-based access control that correctly protects the sibling job events endpoint. The exposure is limited to confidentiality: no job data can be modified and there is no availability impact, consistent with the Red Hat CVSS 3.1 score of 5.0 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N), which matches the upstream CVE assessment. The affected products are Red Hat Ansible Automation Platform 2.5, 2.6, and 2.7 (automation-controller and the controller containers); a fix is being pursued for those streams. The Ansible Automation Platform 2.4 stream was closed without a fix, so environments remaining on that stream stay exposed to this cross-tenant information disclosure.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5N/A5
Attack VectorNetworkN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeChangedN/AChanged
ConfidentialityLowN/ALow
Integrity ImpactNoneN/ANone
Availability ImpactNoneN/ANone

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

cve.org: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Application Data; Read Files or Directories

An attacker could read sensitive data, either by reading the data directly from a data store that is not restricted, or by accessing insufficiently-protected, privileged functionality to read the data.

Integrity

Technical Impact: Modify Application Data; Modify Files or Directories

An attacker could modify sensitive data, either by writing the data directly to a data store that is not restricted, or by accessing insufficiently-protected, privileged functionality to write the data.

Access Control

Technical Impact: Gain Privileges or Assume Identity; Bypass Protection Mechanism

An attacker could gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)

An attacker could gain unauthorized access to resources on the system and excessively consume those resources, leading to a denial of service.

Acknowledgements

This issue was discovered by Chris Meyers (Red Hat).

Frequently Asked Questions

Want to get errata notifications? Sign up here.