Skip to content
VulniPulse
Advisory severityMedium6.7Red Hat Linux

Medium [CVE-2025-9907] Event-driven-ansible: event stream test mode exposes sensitive headers in aap eda

This medium-severity Red Hat Linux advisory covers CVE-2025-9907 affecting Red Hat Ansible Automation Platform 2.5 for RHEL 8, Red Hat Ansible Automation Platform 2.5 for RHEL 9, Red Hat Ansible Automation Platform 2.6 for RHEL 9.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2025-9907 Source published Source updated

VulniPulse record published

CVE-2025-9907
Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Summary

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.

This issue is classified as Moderate because the exposure of sensitive headers, including client Authorization tokens and internal infrastructure values such as X-Trusted-Proxy, can lead to credential leakage and privilege escalation only after user forced mistake and with specific configuration.

Exploitation does not require complex conditions—any user with read access to the event stream can retrieve the headers once a request has been posted in test mode. Exploitation depends on either a user mistakenly sending credentials to the event stream endpoint or internal headers being injected when the wrong path is used.

The persistence of captured headers further increases risk, as sensitive values remain accessible until explicitly overwritten or deleted. Red Hat severity: Moderate — CVSS 6.7 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H).

Is CVE-2025-9907 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2025-9907 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2025-9907?

Upgrade to a fixed release named by Red Hat:

  • ansible-builder-0:3.1.1-1.el8ap
  • ansible-creator-0:25.12.0-1.el8ap
  • ansible-dev-environment-0:25.12.2-1.1.el8ap
  • ansible-dev-tools-0:25.12.0-1.el8ap
  • ansible-lint-0:25.12.0-1.el8ap
  • ansible-navigator-0:25.12.0-1.el8ap
  • ansible-sign-0:0.1.4-1.el8ap
  • automation-eda-controller-0:1.1.14-1.el8ap
  • automation-hub-0:4.10.10-1.el8ap
  • bindep-0:2.13.0-1.el8ap
  • molecule-0:25.12.0-1.el8ap
  • python3.11-ansible-compat-0:25.12.0-1.el8ap

32 more fixed releases are listed below.

Confirm against the vendor advisory before you patch.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.

Official advisory · high-confidence parse· fetched 5 days ago·verify at source

Fixed versions
  • ansible-builder-0:3.1.1-1.el8ap
  • ansible-creator-0:25.12.0-1.el8ap
  • ansible-dev-environment-0:25.12.2-1.1.el8ap
  • ansible-dev-tools-0:25.12.0-1.el8ap
  • ansible-lint-0:25.12.0-1.el8ap
  • ansible-navigator-0:25.12.0-1.el8ap
  • ansible-sign-0:0.1.4-1.el8ap
  • automation-eda-controller-0:1.1.14-1.el8ap
  • automation-hub-0:4.10.10-1.el8ap
  • bindep-0:2.13.0-1.el8ap
  • molecule-0:25.12.0-1.el8ap
  • python3.11-ansible-compat-0:25.12.0-1.el8ap
  • python3.11-distlib-0:0.4.0-1.el8ap
  • python3.11-django-0:4.2.26-1.el8ap
  • python3.11-execnet-0:2.1.2-1.el8ap
  • python3.11-galaxy-importer-0:0.4.36-2.el8ap
  • python3.11-galaxy-ng-0:4.10.10-1.el8ap
  • python3.11-gunicorn-0:23.0.0-1.el8ap
  • python3.11-pluggy-0:1.6.0-1.el8ap
  • python3.11-pytest-0:9.0.1-1.el8ap
  • python3.11-pytest-ansible-0:25.12.0-1.el8ap
  • python3.11-pytest-xdist-0:3.8.0-1.el8ap
  • python3.11-ruamel-yaml-clib-0:0.2.15-1.el8ap
  • python3.11-subprocess-tee-0:0.4.2-1.el8ap
  • python3.11-tox-ansible-0:25.12.0-1.2.el8ap
  • python3.11-typing-extensions-0:4.15.0-1.el8ap
  • ansible-builder-0:3.1.1-1.el9ap
  • ansible-creator-0:25.12.0-1.el9ap
  • ansible-dev-environment-0:25.12.2-1.1.el9ap
  • ansible-dev-tools-0:25.12.0-1.el9ap
  • ansible-lint-0:25.12.0-1.el9ap
  • ansible-navigator-0:25.12.0-1.el9ap
  • ansible-sign-0:0.1.4-1.el9ap
  • automation-eda-controller-0:1.1.14-1.el9ap
  • automation-hub-0:4.10.10-1.el9ap
  • bindep-0:2.13.0-1.el9ap
  • molecule-0:25.12.0-1.el9ap
  • python3.11-ansible-compat-0:25.12.0-1.el9ap
  • python3.11-distlib-0:0.4.0-1.el9ap
  • python3.11-django-0:4.2.26-1.el9ap
  • RHSA-2025:23069
  • RHSA-2025:19201
  • RHSA-2025:23131
  • RHSA-2025:19221

Official advisory · high-confidence parse· fetched 5 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Official advisory · high-confidence parse· fetched 5 days ago·verify at source

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat
All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.