Ansible Automation PlatformApplication · Redhat
CVE-2025-9909
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA flaw was found in the Red Hat Ansible Automation Platform Gateway route creation component. This vulnerability allows credential theft via the creation of misleading routes using a double-slash (//) prefix in the gateway_path. A malicious or socially engineered administrator can configure a honey-pot route to intercept and exfiltrate user credentials, potentially maintaining persistent access or creating a backdoor even after their permissions are revoked.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA path traversal vulnerability in Red Hat Ansible Automation Platform Gateway's route creation component allows a malicious administrator to create routes with a double-slash (//) prefix in the gateway_path parameter. This enables the creation of deceptive honey-pot routes that can intercept and exfiltrate user credentials, providing persistent access even after the attacker's administrative permissions are revoked.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Ansible Automation PlatformApplication
< 2.6
Ansible DeveloperApplication
= 1.2= 1.3
Ansible InsideApplication
= 1.3= 1.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Ansible Gateway versionCheck the installed version of Red Hat Ansible Automation Platform Gateway by reviewing the RPM package, container image tag, or the /manifests/version file in the installation directory. Use commands like 'rpm -qa | grep ansible-gateway' or 'docker images' if containerized.Affected if The installed version is less than 2.6 for Ansible Automation Platform, or exactly 1.2 or 1.3 for Ansible Developer, or exactly 1.3 or 1.4 for Ansible Inside.
-
Review gateway route configurations for double-slash prefixesAccess the API Gateway configuration or route definition files. Query the API or inspect YAML/JSON route configuration files for any gateway_path values that start with '//' or contain '//' patterns that could indicate path traversal.Affected if Any route exists with a gateway_path parameter beginning with double slashes (//).
-
Audit routes that may intercept authentication trafficExamine all configured routes, particularly those handling authentication endpoints (such as /login, /auth, /token, /sso). Identify routes with suspicious or unexpected destination endpoints that could capture credentials.Affected if Routes exist that point to unintended endpoints and could intercept user credentials, especially routes with // prefixes.
-
Check for recently created routes with non-standard pathsReview route creation logs or audit trails for routes created with unusual gateway_path values. Look for routes created outside normal deployment processes.Affected if Routes with anomalous path patterns were created, particularly by administrators with now-revoked permissions.
A system is affected if it runs an affected version AND contains routes with double-slash (//) prefixes in the gateway_path parameter that could intercept credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.6
Implement strict input validation on the gateway_path parameter to reject paths starting with double slashes or other suspicious path patterns. Additionally, add routing logic verification to ensure routes resolve to legitimate endpoints and consider implementing route audit logging to detect credential interception attempts.
Ansible Automation Platform: 2.6 or later; Ansible Developer/Inside: Contact Red Hat support for patch/upgrade guidance
- 1. Identify the current installed version of Red Hat Ansible Automation Platform
- 2. For Ansible Automation Platform: Upgrade to version 2.6 or later to remediate the gateway route creation vulnerability
- 3. For Ansible Developer versions 1.2 and 1.3: Contact Red Hat support for specific patch information or upgrade path
- 4. For Ansible Inside versions 1.3 and 1.4: Contact Red Hat support for specific patch information or upgrade path
- 5. After upgrading, verify that routes are not created with double-slash (//) prefixes in the gateway_path
- 6. Review all existing custom route configurations for potential honey-pot routes that may have been created
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ansible Automation Platform
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9909 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9909 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data