CVE-2025-59343VulnerabilityPublished 22 Oct 2025Updated 21 Oct 2026

Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.5 Product Security and Bug Fix Update

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2025-59682

Authoritative record:CVE-2025-59343· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade Red Hat to 2.6.0 soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

8.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.6.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: High
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

bundesamt-f-r-sicherheit-in-de

What to do

Upgrade Red Hat to 2.6.0.

Affected software

Product	Affected	Fixed in
Red Hat Product Security Red Hat	Affected >=2.5.0 <2.6.0 Red Hat Red Hat Ansible Automation Platform Red Hat Ansible Automation Platform 2.5 for RHEL 9	Fixed in 2.6.0

AI-suggested

Red Hat has released updated packages for Ansible Automation Platform 2.5 that address these vulnerabilities. Users should apply the official security update RHSA-2025:18979 promptly to remediate these issues. The advisory includes updated versions of automation-gateway (2.5.20251022), automation-gateway-proxy, python3.11-django-ansible-base, and other components. No additional mitigation steps are indicated beyond applying the official patches.

Description

Red Hat Ansible Automation Platform provides an enterprise framework for building, deploying and managing IT automation at scale. IT Managers can provide top-down guidelines on how automation is applied to individual teams, while automation developers retain the freedom to write tasks that leverage existing knowledge without the overhead. Ansible Automation Platform makes it possible for users across an organization to share, vet, and manage automation content by means of a simple, powerful, and agentless language. Security Fix(es): * python3.11-django: Potential partial directory-traversal via archive.extract() (CVE-2025-59682) * automation-gateway: tar-fs symlink validation bypass (CVE-2025-59343) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. Updates and fixes included: Automation Platform * Azure AD authentication now searches more fields to find the username override field specified. If not found it will log a warning message indicating which fields are valid (AAP-53789) * Support TLSv1.3 on server-to-server requests, where previously services which only supported TLSv1.3 would not work (AAP-49456) * Added a step in the subscription wizard that allows the user to configure automation analytics (AAP-55094) * Subscription credentials can no longer be viewed/edited from the system settings page (AAP-55014) * Fixed an issue where the settings displayed "Red Hat" inconsistently in the API and UI (AAP-54277) * Fixed a bug where platform auditors were not able to see Automation Execution and Platform level settings (AAP-53975) * Fixed an issue where some fields were missing the autocomplete = new-password setting (AAP-53934) * Fixed an issue where AAP could not set/create a playbook when using branch override (AAP-52566) * Empty strings are no longer displayed in the extra variables field on the Jobs > Details page (AAP-49448) * Added two new toggle options on the subscription wizard to allow for fetching subscriptions using basic authentication (AAP-47865) * Fixed validation of prompt-on-launch credentials in a workflow job template (AAP-40540) * Fixed an issue for comments in extra vars sections, all comments in YAML are now persisted on create and edit operations for a resource (AAP-37071) * Updated error handling in the Authenticator form to match other forms in the Platform UI (AAP-22928) * automation-gateway has been updated to 2.5.20251022 * automation-gateway-proxy has been updated to 2.5.10-3 for RHEL8 * automation-gateway-proxy has been updated to 2.6.6-4 for RHEL9 * python3.11-django-ansible-base has been updated to 2.5.20251022 Automation controller * Fixed an issue where the ansible.platform collection did not work with the default Red Hat Ansible Automation Platform credential type (AAP-55685) * Fixed an issue in callback receiver and dispatcher crash loop state caused by re-running the installer with modified inventory hostname (AAP-55638) * Added support for Red Hat username and password for the subscription management API (AAP-54976) * Fixes system_administrator role creation race condition which most commonly happened on new openshift deployments resulting in the default instance group not being created (AAP-54964) * Fixed an issue where Grafana notifications couldn't have an empty dashboard ID or panel ID (AAP-54654) * Improved stability on long-running jobs, clusters under heavy load and network flakiness in receptor (AAP-53742) * Fixed Platform Auditor to view controller settings (AAP-53345) * Added missing instruction to set an environment variable in the CLI in order to achieve compatibility with the current release (AAP-37812) * Fixed Platform Auditor to view Metrics API endpoint (AAP-36492) * automation-controller has been updated to 4.6.21 * receptor has been updated to 1.6.0 Automation hub * Fixed an issue where _ui/v2/ user detail displayed the data correctly (AAP-55957) * automation-hub has been updated to 4.10.9 * python3.11-galaxy-ng has been updated to 4.10.9 * python3.11-galaxy-importer has been updated to 0.4.34 Container-based Ansible Automation Platform * Set REDHAT_CANDLEPIN_VERIFY to correct CA pem so that controller can make requests to subscription.rhsm.redhat.com (AAP-55181) * Implemented preflight ansible-core version validation (AAP-54931) * Fixed a bug where Ansible would fail to gather the system's UUID for Linux on Power (AAP-54540) * containerized installer setup has been updated to 2.5-20 RPM-based Ansible Automation Platform * Fixed an issue where setting automationgateway_disable_https=false resulted in install failure (AAP-55475) * Set REDHAT_CANDLEPIN_VERIFY to correct CA pem so that controller can make requests to subscription.rhsm.redhat.com (AAP-55184) * Fixed issue where RESOURCE_KEY SECRET_KEY was not updated when restoring from a different environment (AAP-54944) * Fixed issue where EDA DE credentials fa

Impact

Successful exploitation of these vulnerabilities could allow an attacker to bypass security restrictions related to file extraction and symbolic link validation, potentially leading to unauthorized file access or modification within the Ansible Automation Platform environment. This could compromise the integrity of automation tasks or expose sensitive data. The vulnerabilities are rated with high severity by Red Hat Product Security.

Summary

This advisory covers two security fixes in Red Hat Ansible Automation Platform 2.5: CVE-2025-59343 is a symlink validation bypass vulnerability in the automation-gateway's tar-fs handling, which could allow an attacker to bypass security checks on symbolic links during archive extraction. CVE-2025-59682 is a potential partial directory-traversal vulnerability in python3.11-django's archive.extract() function, which could allow unauthorized access to filesystem paths. The advisory includes updates to automation-gateway, python3.11-django-ansible-base, and other components to remediate these issues. Additional bug fixes and feature improvements are also included in this release.

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Aug 2026, 16:48 UTC

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats