dbcve.org
Ansible Automation PlatformApplication · Redhat

CVE-2025-9908

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 Streams. This vulnerability allows an authenticated user to gain access to sensitive internal infrastructure headers (such as X-Trusted-Proxy and X-Envoy-*) and event stream URLs via crafted requests and job templates. By exfiltrating these headers, an attacker could spoof trusted requests, escalate privileges, or perform malicious event injection.

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

This is an information disclosure vulnerability in Red Hat Ansible Automation Platform's Event-Driven Ansible (EDA) Event Streams. An authenticated user can craft specific requests or job templates to leak sensitive internal infrastructure headers (X-Trusted-Proxy, X-Envoy-*) and event stream URLs. These headers can then be used to spoof trusted requests, escalate privileges, or inject malicious events into the system.

MitigationApply the vendor-provided patch or update to the Ansible Automation Platform EDA component. Review and restrict access to event stream configurations and job templates to limit exposure of internal header information.

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. Check Ansible Automation Platform version
    Run 'ansible-automation-platform --version' or check the AAP installation manifest for the version number
    Affected if Version is less than 2.6 (for AAP), or equals 1.2 or 1.3 (for Developer), or equals 1.3 or 1.4 (for Inside)
  2. Verify EDA Event Streams are configured
    Check if Event-Driven Ansible event streams or rulebook activations are enabled in the AAP controller interface or via 'eda-activation' CLI commands
    Affected if EDA event streams or rulebook activations are active in the environment
  3. Inspect job templates for header exposure
    Review existing job templates in the Ansible controller for any custom configurations that may reference or output HTTP headers, particularly X-Trusted-Proxy or X-Envoy-* headers
    Affected if Job templates exist that capture or expose internal infrastructure headers in their output or logs
  4. Review event stream configurations
    Examine event stream configurations in the EDA settings for any URLs or headers that may be logged or returned in job output
    Affected if Event stream configurations are present and may expose internal endpoint URLs or headers
  5. Check for sensitive headers in logs
    Search automation controller and EDA logs for presence of X-Trusted-Proxy, X-Envoy-* headers or internal event stream URLs in job output or audit logs
    Affected if Logs contain internal infrastructure headers or internal event stream URLs that should not be visible to users

User is affected if running a vulnerable version (AAP < 2.6, Developer 1.2/1.3, Inside 1.3/1.4) AND EDA Event Streams are configured or active in the environment.

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

Apply the vendor-provided patch or update to the Ansible Automation Platform EDA component. Review and restrict access to event stream configurations and job templates to limit exposure of internal header information.

Recommended fix High confidence

Red Hat Ansible Automation Platform 2.6

  1. Upgrade Red Hat Ansible Automation Platform to version 2.6 or later to remediate the information exposure vulnerability in Event-Driven Ansible (EDA) Event Streams
  2. After upgrading, verify that the X-Trusted-Proxy, X-Envoy-*, and event stream URL information is no longer accessible to authenticated users through crafted requests
  3. Test any job templates that interact with event streams to ensure functionality is maintained after the upgrade
  4. Review user permissions and role assignments in the upgraded environment to ensure proper access controls are in place
Caveat Major platform upgrades may introduce changes to automation workflows, EDA rules, or integrations that require testing and potential adjustments

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

Fix this in Ansible Automation Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9908 — 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-9908 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