Unauthenticated event-stream injection via forged Subject header
Published Jul 31, 2026 · Updated Jul 31, 2026
Authentication bypass in Red Hat Ansible Automation Platform 2.6 allows remote attackers to inject events into mTLS-protected EDA streams. The aap-gateway configuration accepts a forged HTTP Subject header after event-stream URL manipulation instead of binding the request to the client certificate, and an error reveals the expected subject. Network access to an EDA event-stream endpoint is sufficient, and injected events can trigger configured automated workflows.
Summary
What happened
Authentication bypass in Red Hat Ansible Automation Platform 2.6 allows remote attackers to inject events into mTLS-protected EDA streams. The aap-gateway configuration accepts a forged HTTP Subject header after event-stream URL manipulation instead of binding the request to the client certificate, and an error reveals the expected subject. Network access to an EDA event-stream endpoint is sufficient, and injected events can trigger configured automated workflows.
The record
- CVE
- CVE-2026-18141
- Published
- Jul 31, 2026
- Updated
- Jul 31, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Ansible Automation Platform
- Classifications
- CWE-295, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 31, 2026CVE publishedPublication date reported by the CVE source.
- Jul 31, 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