Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14025: Incorrect Execution-Assigned Permissions in Red Hat Red Hat Ansible Automation Platform 2.5 for RHEL 8

0
High
VulnerabilityCVE-2025-14025cvecve-2025-14025
Published: Thu Jan 08 2026 (01/08/2026, 13:44:04 UTC)
Source: CVE Database V5
Vendor/Project: Red Hat
Product: Red Hat Ansible Automation Platform 2.5 for RHEL 8

Description

A flaw was found in Ansible Automation Platform (AAP). Read-only scoped OAuth2 API Tokens in AAP, are enforced at the Gateway level for Gateway-specific operations. However, this vulnerability allows read-only tokens to perform write operations on backend services (e.g., Controller, Hub, EDA). If this flaw were exploited, an attacker‘s capabilities would only be limited by role based access controls (RBAC).

AI-Powered Analysis

AILast updated: 01/08/2026, 14:19:37 UTC

Technical Analysis

CVE-2025-14025 is a vulnerability identified in Red Hat Ansible Automation Platform 2 that involves incorrect enforcement of execution-assigned permissions for OAuth2 API tokens. Specifically, read-only scoped OAuth2 tokens, which should be limited to Gateway-specific read operations, can be exploited to perform unauthorized write operations on backend services such as the Controller, Hub, and Event-Driven Automation (EDA) components. This occurs because the enforcement of token scopes is only applied at the Gateway level, failing to restrict backend service operations adequately. Consequently, an attacker possessing a read-only token can escalate their privileges within the platform, constrained only by the existing role-based access control (RBAC) configurations. The vulnerability has a CVSS v3.1 base score of 8.5, reflecting high severity, with attack vector being network-based, requiring low privileges, no user interaction, and impacting confidentiality, integrity, and availability with a scope change. Although no exploits have been reported in the wild yet, the flaw presents a significant risk, especially in environments where automation platforms manage critical infrastructure or sensitive operations. The vulnerability was reserved in December 2025 and published in January 2026, indicating recent discovery and disclosure. The lack of currently available patches necessitates immediate attention to access control policies and token management to mitigate potential exploitation.

Potential Impact

For European organizations, the impact of CVE-2025-14025 can be substantial. Ansible Automation Platform is widely used for orchestrating IT infrastructure, deploying applications, and managing configurations across diverse environments. Exploitation could allow attackers to perform unauthorized write operations, potentially leading to unauthorized configuration changes, deployment of malicious code, data leakage, or disruption of automated workflows. This undermines the confidentiality, integrity, and availability of critical systems and data. Organizations in sectors such as finance, telecommunications, manufacturing, and government, which rely heavily on automation for operational efficiency and security, may face increased risk of operational disruption and data breaches. The vulnerability could also facilitate lateral movement within networks if attackers leverage compromised automation workflows. Given the high CVSS score and the scope of affected components, the threat could lead to severe operational and reputational damage if exploited.

Mitigation Recommendations

1. Monitor Red Hat advisories closely and apply security patches or updates for Ansible Automation Platform 2 as soon as they become available. 2. Conduct a thorough audit of OAuth2 token scopes and RBAC policies to ensure that tokens are granted the minimum necessary privileges and that role assignments are strictly controlled. 3. Restrict the issuance of read-only OAuth2 tokens and consider implementing additional validation or multi-factor authentication for token generation. 4. Implement network segmentation and access controls to limit exposure of backend services (Controller, Hub, EDA) to only trusted components and users. 5. Enable detailed logging and monitoring of API token usage to detect anomalous write operations originating from tokens expected to have read-only permissions. 6. Review and harden automation workflows to detect and prevent unauthorized changes triggered via compromised tokens. 7. Educate administrators and DevOps teams about the risks of token misuse and enforce strict operational security practices around automation platform credentials.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
redhat
Date Reserved
2025-12-04T12:33:19.376Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695fb9abc901b06321f2a5e3

Added to database: 1/8/2026, 2:05:31 PM

Last enriched: 1/8/2026, 2:19:37 PM

Last updated: 1/9/2026, 9:55:07 AM

Views: 38

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats