CVE-2026-94416

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreHIGH confidence

Score 6.8 from GitHub Security Advisory published 2026-09-24. a secondary CVSS source baseline 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
Trending — 3 sources updated this week
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 6.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An authorization bypass was found in the Ansible Automation Platform (AAP) gateway. The gateway API allows an authenticated administrator to create a new service key for the Controller service cluster. Because service-key creation is not restricted to the installer-provisioned provisioning path, an administrator-issued key is cryptographically indistinguishable from a legitimate one and can be used to forge a service-authentication token that impersonates the Controller service. Combined with the gateway OIDC workload-identity endpoint (enabled via FEATURE_OIDC_WORKLOAD_IDENTITY_ENABLED), the attacker can drive the gateway to sign Workload Identity Tokens (WITs) for arbitrary Controller workloads. A downstream resource server such as HashiCorp Vault that trusts the gateway OIDC key will accept the forged WIT and return the AAP credentials bound to that workload, disclosing secrets beyond the attacker's authorization boundary.

CVSS v3
6.8
EG Score
6.8(high)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity68% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

September 24, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Sep 24, 2026
Patch available. Sources: github_pr, redhat.
github_pr

[WIP][AAP-65516] Removing POST option from service_keys endpoint

Upstream fix in progress (PR #235 · ansible/jewel, state=open)

https://github.com/ansible/jewel/pull/235
github_pr

[AAP-65516] Limit service key module to existing keys

Upstream fix in progress (PR #254 · ansible/ansible.platform, state=open)

https://github.com/ansible/ansible.platform/pull/254
redhat Patch Available

CVE-2026-94416 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-94416

Vendor Advisories for CVE-2026-94416(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 5× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 16:36 UTCEG score recompute
  2. 2026-09-24 16:36 UTCGHSA enrichment
  3. 2026-09-24 13:24 UTCEG score recompute
  4. 2026-09-24 12:47 UTCEG score recompute
  5. 2026-09-24 12:47 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-94416?
CVE-2026-94416 is a medium vulnerability published on September 24, 2026. An authorization bypass was found in the Ansible Automation Platform (AAP) gateway. The gateway API allows an authenticated administrator to create a new service key for the Controller service cluster. Because service-key creation is not restricted to the installer-provisioned provisioning path, an…
When was CVE-2026-94416 disclosed?
CVE-2026-94416 was first published in the National Vulnerability Database on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-94416?
CVE-2026-94416 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-94416?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-94416, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-94416

Explore →

Is Your Infrastructure Affected by CVE-2026-94416?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.