Credential disclosure via persisted test-mode headers
Published Feb 27, 2026 · Updated Feb 27, 2026
Information disclosure in Red Hat Ansible Automation Platform 2.5 and 2.6 allows remote authenticated users to read sensitive HTTP headers. The Event Stream API captures every incoming header in test_headers and persists the field without redacting Authorization or trusted-proxy values. Exposure requires test mode and event-stream read access; leaked headers remain visible and permit credential reuse when they contain valid tokens.
Summary
What happened
Information disclosure in Red Hat Ansible Automation Platform 2.5 and 2.6 allows remote authenticated users to read sensitive HTTP headers. The Event Stream API captures every incoming header in test_headers and persists the field without redacting Authorization or trusted-proxy values. Exposure requires test mode and event-stream read access; leaked headers remain visible and permit credential reuse when they contain valid tokens.
The record
- CVE
- CVE-2025-9907
- Published
- Feb 27, 2026
- Updated
- Feb 27, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Ansible Automation Platform
- Classifications
- CWE-200, T1552
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 27, 2026CVE publishedPublication date reported by the CVE source.
- Feb 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo