Authenticated backend writes via token scope bypass
Published Jan 8, 2026 · Updated Jan 8, 2026
Authorization bypass in Red Hat Ansible Automation Platform 2.5 and 2.6 allows remote authenticated users to perform backend writes. The platform gateway enforces read-only OAuth2 token scope on gateway operations but forwards access to Controller, Hub, and EDA without preserving that write restriction. A valid read-only token is required, and resulting changes remain limited by the token holder's RBAC permissions; Red Hat states that the flaw does not elevate privileges.
Summary
What happened
Authorization bypass in Red Hat Ansible Automation Platform 2.5 and 2.6 allows remote authenticated users to perform backend writes. The platform gateway enforces read-only OAuth2 token scope on gateway operations but forwards access to Controller, Hub, and EDA without preserving that write restriction. A valid read-only token is required, and resulting changes remain limited by the token holder's RBAC permissions; Red Hat states that the flaw does not elevate privileges.
The record
- CVE
- CVE-2025-14025
- Published
- Jan 8, 2026
- Updated
- Jan 8, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Ansible Automation Platform
- Classifications
- CWE-279
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 8, 2026CVE publishedPublication date reported by the CVE source.
- Jan 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo