Quick answers
- Is CVE-2026-94416 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-94416 being exploited in the wild.
- How severe is CVE-2026-94416?
- Medium severity, with a CVSS score of 6.8, published 24 September 2026.
- Which products and versions are affected?
- Red Hat Ansible Automation Platform 2.5 through 2.7.
- Is there a fix for CVE-2026-94416?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-94416 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-94416?
- Check whether you run Red Hat Ansible Automation Platform at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An authenticated administrator can create a service key that is cryptographically indistinguishable from installer-provisioned keys due to lack of restriction on the service-key creation path. When FEATURE_OIDC_WORKLOAD_IDENTITY_ENABLED is active, the attacker can forge service-authentication tokens to drive the gateway's OIDC endpoint into signing Workload Identity Tokens for arbitrary Controller workloads, enabling token forgery attacks. A downstream OIDC-trusting resource server will accept the forged WIT and return credentials bound to that workload, disclosing secrets beyond the attacker's authorization boundary.
Affected products
- Red Hat Ansible Automation Platform 2.5 through 2.7
Timeline
- 2026-09-24: disclosed