CVE-2025-53862 json
Aap: aap-gateway: automation-hub: sensitive information disclosure
published 2025-07-11 15 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-21135
- cvss
- 3.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
A flaw was found in Ansible. Three API endpoints are accessible and return verbose, unauthenticated responses. This flaw allows a malicious user to access data that may contain important information.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-53862 updated cvss 3.5
aap: aap-gateway: automation-hub: Sensitive Information Disclosure
-
Red Hat Ansible Automation Platform 2 automation-hub, automation-eda-controller, ansible-automation-platform-25/gateway-rhel8-operatornot affected: component not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 15 mo ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.5 | CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected products
- Red Hat Red Hat Ansible Automation Platform 2
Classification
- Weakness
-
- CWE-497 Exposure of Sensitive System Information to an Unauthorized Control Sphere
References
-
access.redhat.com
/security/cve/CVE-2025-53862
vdb-entry, vendor-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=2379359
issue-tracking
Sources
- CVE List CVE-2025-53862
- NVD CVE-2025-53862
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.