CVE-2026-18141

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-07-31. a secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in aap-gateway, a component of Ansible Automation Platform's Event-Driven Ansible (EDA). An unauthenticated remote attacker can bypass mutual Transport Layer Security (mTLS) authentication for event streams. This is achieved by manipulating the event stream URL and forging the HTTP Subject header. The system also inadvertently discloses the expected certificate subject in error messages, which simplifies the attack. This vulnerability allows an attacker to inject arbitrary events into EDA, potentially triggering automated workflows.

CVSS v3
8.2
EG Score
8.2(high)
EG Risk
52(Track)
EG Risk 52/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
Severity82% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

July 31, 2026

Last Modified

August 4, 2026

Advisory Details (2)

Auto-updated Jul 31, 2026
Patch available. Sources: redhat.
redhat

2508155 – (CVE-2026-18141) CVE-2026-18141 aap-gateway: aap-gateway: Authentication bypass in Event-Driven Ansible via forged HTTP header

https://bugzilla.redhat.com/show_bug.cgi?id=2508155
redhat Patch Available

cve-details

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

Vendor Advisories for CVE-2026-18141(4)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatautomation-eda-controller-0:1.2.11-1.el9ap2026-08-04redhat
redhatansible-automation-platform-27/gateway-rhel9:17854359702026-08-04redhat
redhatansible-automation-platform-26/gateway-rhel9:17857800202026-08-04redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 41× in last 7d / 92× 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-08-15 06:57 UTCEG score recompute
  2. 2026-08-15 06:57 UTCVendor advisory
  3. 2026-08-15 06:57 UTCGHSA enrichment
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 18:28 UTCVendor advisory
  6. 2026-08-14 18:28 UTCGHSA enrichment
  7. 2026-08-14 06:42 UTCEG score recompute
  8. 2026-08-14 06:42 UTCVendor advisory
  9. 2026-08-14 06:42 UTCGHSA enrichment
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-13 18:55 UTCVendor advisory
  12. 2026-08-13 18:55 UTCGHSA enrichment
  13. 2026-08-13 07:09 UTCVendor advisory
  14. 2026-08-13 07:09 UTCGHSA enrichment
  15. 2026-08-13 07:00 UTCGHSA enrichment
  16. 2026-08-12 19:11 UTCEG score recompute
  17. 2026-08-12 19:11 UTCVendor advisory
  18. 2026-08-12 19:11 UTCGHSA enrichment
  19. 2026-08-12 13:50 UTCEPSS rescore
  20. 2026-08-12 07:24 UTCVendor advisory
  21. 2026-08-12 07:24 UTCGHSA enrichment
  22. 2026-08-11 19:37 UTCEG score recompute
  23. 2026-08-11 19:37 UTCVendor advisory
  24. 2026-08-11 19:37 UTCGHSA enrichment
  25. 2026-08-11 13:42 UTCEPSS rescore
Show 67 more
  1. 2026-08-11 07:44 UTCEG score recompute
  2. 2026-08-11 07:44 UTCVendor advisory
  3. 2026-08-11 07:44 UTCGHSA enrichment
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-10 19:58 UTCVendor advisory
  6. 2026-08-10 19:58 UTCGHSA enrichment
  7. 2026-08-10 08:11 UTCVendor advisory
  8. 2026-08-10 08:11 UTCGHSA enrichment
  9. 2026-08-09 20:24 UTCEG score recompute
  10. 2026-08-09 20:24 UTCVendor advisory
  11. 2026-08-09 20:24 UTCGHSA enrichment
  12. 2026-08-09 13:46 UTCEPSS rescore
  13. 2026-08-09 08:38 UTCVendor advisory
  14. 2026-08-09 08:38 UTCGHSA enrichment
  15. 2026-08-08 20:51 UTCVendor advisory
  16. 2026-08-08 20:51 UTCGHSA enrichment
  17. 2026-08-08 09:04 UTCVendor advisory
  18. 2026-08-08 09:04 UTCGHSA enrichment
  19. 2026-08-07 21:18 UTCEG score recompute
  20. 2026-08-07 21:18 UTCVendor advisory
  21. 2026-08-07 21:18 UTCGHSA enrichment
  22. 2026-08-07 09:31 UTCVendor advisory
  23. 2026-08-07 09:31 UTCGHSA enrichment
  24. 2026-08-06 21:44 UTCEG score recompute
  25. 2026-08-06 21:44 UTCVendor advisory
  26. 2026-08-06 21:44 UTCGHSA enrichment
  27. 2026-08-06 13:46 UTCEPSS rescore
  28. 2026-08-06 09:57 UTCVendor advisory
  29. 2026-08-06 09:57 UTCGHSA enrichment
  30. 2026-08-05 22:11 UTCEG score recompute
  31. 2026-08-05 22:11 UTCVendor advisory
  32. 2026-08-05 22:11 UTCGHSA enrichment
  33. 2026-08-05 19:17 UTCEPSS rescore
  34. 2026-08-05 10:24 UTCGHSA enrichment
  35. 2026-08-04 22:32 UTCEG score recompute
  36. 2026-08-04 22:32 UTCGHSA enrichment
  37. 2026-08-04 22:06 UTCEG score recompute
  38. 2026-08-04 22:06 UTCGHSA enrichment
  39. 2026-08-04 21:32 UTCEG score recompute
  40. 2026-08-04 21:32 UTCGHSA enrichment
  41. 2026-08-04 21:13 UTCEG score recompute
  42. 2026-08-04 21:13 UTCGHSA enrichment
  43. 2026-08-04 19:26 UTCEG score recompute
  44. 2026-08-04 19:26 UTCGHSA enrichment
  45. 2026-08-04 18:56 UTCEG score recompute
  46. 2026-08-04 18:56 UTCGHSA enrichment
  47. 2026-08-04 16:31 UTCEG score recompute
  48. 2026-08-04 16:31 UTCGHSA enrichment
  49. 2026-08-04 15:10 UTCEPSS rescore
  50. 2026-08-04 10:38 UTCEPSS rescore
  51. 2026-08-04 04:44 UTCGHSA enrichment
  52. 2026-08-03 16:56 UTCEG score recompute
  53. 2026-08-03 16:56 UTCGHSA enrichment
  54. 2026-08-03 10:35 UTCEPSS rescore
  55. 2026-08-03 06:25 UTCGHSA enrichment
  56. 2026-08-02 18:33 UTCGHSA enrichment
  57. 2026-08-02 06:46 UTCEG score recompute
  58. 2026-08-02 06:46 UTCGHSA enrichment
  59. 2026-08-02 02:26 UTCEPSS rescore
  60. 2026-08-01 18:59 UTCGHSA enrichment
  61. 2026-08-01 07:12 UTCGHSA enrichment
  62. 2026-07-31 19:25 UTCEG score recompute
  63. 2026-07-31 19:24 UTCGHSA enrichment
  64. 2026-07-31 18:43 UTCEG score recompute
  65. 2026-07-31 18:43 UTCGHSA enrichment
  66. 2026-07-31 16:21 UTCEG score recompute
  67. 2026-07-31 16:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-18141?
CVE-2026-18141 is a high vulnerability published on July 31, 2026. A flaw was found in aap-gateway, a component of Ansible Automation Platform's Event-Driven Ansible (EDA). An unauthenticated remote attacker can bypass mutual Transport Layer Security (mTLS) authentication for event streams. This is achieved by manipulating the event stream URL and forging the HTTP…
When was CVE-2026-18141 disclosed?
CVE-2026-18141 was first published in the National Vulnerability Database on July 31, 2026, with the most recent update on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18141 actively exploited?
CVE-2026-18141 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.6% of all scored CVEs.
What is the CVSS score of CVE-2026-18141?
CVE-2026-18141 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-18141?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18141, 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-18141

Explore →

Is Your Infrastructure Affected by CVE-2026-18141?

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

Start Free Scan →Browse All CVEs