CVE-2025-9909
Credential Theft via Route Manipulation in Red Hat Ansible Gateway
Publication date: 2026-02-27
Last updated on: 2026-03-25
Assigner: Red Hat, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| redhat | ansible_developer | 1.2 |
| redhat | ansible_inside | 1.3 |
| redhat | ansible_automation_platform | to 2.6 (exc) |
| redhat | ansible_developer | 1.3 |
| redhat | ansible_inside | 1.4 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-647 | The product defines policy namespaces and makes authorization decisions based on the assumption that a URL is canonical. This can allow a non-canonical URL to bypass the authorization. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Red Hat Ansible Automation Platform Gateway route creation component. It involves the use of a double-slash (//) prefix in the gateway_path to create misleading routes.
A malicious or socially engineered administrator can exploit this flaw by configuring a honey-pot route that intercepts and steals user credentials.
This allows the attacker to potentially maintain persistent access or create a backdoor even after their permissions have been revoked.
How can this vulnerability impact me? :
The vulnerability can lead to credential theft by intercepting user credentials through misleading routes.
An attacker with administrative access can maintain persistent unauthorized access or create a backdoor, compromising the security of the system.
This can result in a high impact on confidentiality, integrity, and availability of the affected system, as indicated by the CVSS score of 6.7.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know