dbcve.org
Ansible Automation PlatformApplication · Redhat

CVE-2025-9907

MEDIUM · 6.7 CVSS v3.1 Published 2026-02-27
Fix available
A fix is available. Upgrade to 2.6 or later.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

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 · unedited
A flaw was found in the Red Hat Ansible Automation Platform, Event-Driven Ansible (EDA) Event Stream API. This vulnerability allows exposure of sensitive client credentials and internal infrastructure headers via the test_headers field when an event stream is in test mode. The possible outcome includes leakage of internal infrastructure details, accidental disclosure of user or system credentials, privilege escalation if high-value tokens are exposed, and persistent sensitive data exposure to all users with read access on the event stream.

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 confidence

The Event-Driven Ansible Event Stream API has an information disclosure vulnerability where the test_headers field exposes sensitive client credentials and internal infrastructure headers when an event stream operates in test mode. Users with read access on the event stream can view these credentials, potentially leading to privilege escalation if high-value tokens are exposed and persistent sensitive data disclosure.

MitigationRestrict access to the test_headers field in test mode, implement credential masking/redaction for all sensitive values displayed in the API, and enforce stricter access controls on event stream configurations containing sensitive data.

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
Affected:< 2.6
Ansible DeveloperApplication
Affected:= 1.2= 1.3
Ansible InsideApplication
Affected:= 1.3= 1.4

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Ansible product and version
    Run 'ansible-core --version' or check the Redhat Ansible Automation Platform (AAP), Developer, or Inside version via the package manager or web UI. Compare against affected versions: AAP < 2.6, Developer = 1.2 or 1.3, Inside = 1.3 or 1.4.
    Affected if The installed version falls within the affected ranges listed.
  2. Locate Event Stream configurations
    Access the Ansible Automation Platform controller UI or API and navigate to Event-Driven Ansible > Event Streams. Identify any configured event streams.
    Affected if Any event stream resource exists in the environment.
  3. Determine if event streams operate in test mode
    For each event stream, inspect the configuration for a 'test_mode' or 'test' setting. This may be visible in the event stream details API endpoint (GET /api/eda/v1/event_streams/) or UI.
    Affected if Any event stream has test mode or test mode functionality enabled.
  4. Inspect test_headers field for exposed credentials
    If test mode is enabled, query the event stream details API or UI to retrieve the 'test_headers' field. Examine the headers for any sensitive values such as tokens, passwords, API keys, authorization credentials, or internal infrastructure headers (e.g., X-Internal-Token).
    Affected if The test_headers field is populated with unredacted sensitive credentials or internal tokens.
  5. Verify user access to event stream data
    Check which users or roles have read access to event stream configurations. Review permissions for users with viewer or auditor roles who could access the test_headers field.
    Affected if Users with read-only access can view the event stream configuration containing test_headers.

A user is affected if they run an affected Ansible product version, have event streams with test mode enabled, and possess users with read access to event streams where sensitive credentials are exposed in the test_headers field.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.6 or later
Fixed in 2.6
Interim mitigation

Restrict access to the test_headers field in test mode, implement credential masking/redaction for all sensitive values displayed in the API, and enforce stricter access controls on event stream configurations containing sensitive data.

Recommended fix Moderate confidence

Ansible Automation Platform 2.6 or later (for Ansible Developer and Ansible Inside, consult Red Hat support for specific fixed versions)

  1. Identify the current Ansible Automation Platform version in use by checking the UI or running 'ansible-controller --version' or 'awx-manage --version'
  2. Confirm the deployment is using Event-Driven Ansible (EDA) functionality with event streams
  3. Plan maintenance window for upgrade to avoid disruption
  4. For Ansible Automation Platform, upgrade to version 2.6 or later which contains the fix for the test_headers information exposure
  5. After upgrade, verify the Event Stream API test mode no longer exposes sensitive credentials or internal headers in the test_headers field
  6. Review event stream configurations to ensure no residual exposure of credentials in test mode
Caveat Review Ansible Automation Platform 2.6 release notes for any breaking changes related to EDA or event streams before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ansible Automation Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9907 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9907 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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