A massive distribution of SmartLoader malware has been discovered through GitHub repositories masquerading as legitimate projects. These repositories focus on topics like game cheats, software cracks, and automation tools to attract users. The malware is distributed via compressed files containing a legitimate Lua loader executable, a malicious batch file, and an obfuscated Lua script. Once executed, SmartLoader establishes persistence, sends system information to a C2 server, and downloads additional payloads. The malware has been observed downloading InfoStealer malware such as Rhadamanthys, Redline, and Lumma Stealer. Users are advised to download software only from official sources and to carefully verify the credibility of GitHub repositories before use.
A Regular Expression Denial of Service (ReDoS) vulnerability (CVE-2025-2099) was identified in the ansible-lightspeed-chatbot-container component of Red Hat Ansible Automation Platform 2.5. This vulnerability is related to the huggingface/transformers library. Red Hat has released an update for Ansible Automation Platform 2.5 that addresses this issue along with updates to several Ansible collections.
Red Hat Ansible Automation Platform 2.5 has two security vulnerabilities addressed in a moderate severity advisory. The first vulnerability (CVE-2025-5988) involves disabled CSRF origin checking in the automation-gateway component. The second vulnerability (CVE-2025-7738) involves sensitive authenticator secrets being returned in clear text via the API in the python3.11-django-ansible-base component. Red Hat has released updates for these components and other bug fixes as part of the 2.5.20250730 update. The advisory covers multiple architectures and RHEL 8 and 9 versions of the platform.
Coyote in the Wild: First-Ever Malware That Abuses UI Automation
Source: https://www.akamai.com/blog/security-research/active-exploitation-coyote-malware-first-ui-automation-abuse-in-the-wild
A flaw was found in Ansible. Sensitive cookies without security flags over non-encrypted channels can lead to Man-in-the-Middle (MitM) and Cross-site scripting (XSS) attacks allowing attackers to read transmitted data.
Red Hat Ansible Automation Platform 2.5 has multiple security vulnerabilities including request smuggling due to acceptance of invalid chunked data, template injection via Git branch and refspec, and authenticated argument injection in Git URL during EDA project creation. These issues affect components such as automation-eda-controller, automation-gateway-proxy, and receptor. The update includes security fixes addressing these vulnerabilities along with various bug fixes and improvements.
The Recover WooCommerce Cart Abandonment, Newsletter, Email Marketing, Marketing Automation By FunnelKit plugin for WordPress is vulnerable to unauthorized arbitrary plugin installation due to a missing capability check on the install_or_activate_addon_plugins() function and a weak nonce hash in all versions up to, and including, 3.5.3. This makes it possible for unauthenticated attackers to install arbitrary plugins on the site that can be leveraged to further infect a vulnerable site.
Conda-build contains commands and tools to build conda packages. Prior to version 25.3.1, the write_build_scripts function in conda-build creates the temporary build script conda_build.sh with overly permissive file permissions (0o766), allowing write access to all users. Attackers with filesystem access can exploit a race condition to overwrite the script before execution, enabling arbitrary code execution under the victim's privileges. This risk is significant in shared environments, potentially leading to full system compromise. Even with non-static directory names, attackers can monitor parent directories for file creation events. The brief window between script creation (with insecure permissions) and execution allows rapid overwrites. Directory names can also be inferred via timestamps or logs, and automation enables exploitation even with semi-randomized paths by acting within milliseconds of detection. This issue has been patched in version 25.3.1. A workaround involves restricting conda_build.sh permissions from 0o766 to 0o700 (owner-only read/write/execute). Additionally, use atomic file creation (write to a temporary randomized filename and rename atomically) to minimize the race condition window.
Nautobot is a Network Source of Truth and Network Automation Platform. Prior to v2.4.10 and v1.6.32 , files uploaded by users to Nautobot's MEDIA_ROOT directory, including DeviceType image attachments as well as images attached to a Location, Device, or Rack, are served to users via a URL endpoint that was not enforcing user authentication. As a consequence, such files can be retrieved by anonymous users who know or can guess the correct URL for a given file. Nautobot v2.4.10 and v1.6.32 address this issue by adding enforcement of Nautobot user authentication to this endpoint.
Red Hat Ansible Automation Platform 2.4 Container Release Update addresses a security vulnerability in the ansible-lightspeed-container component where the h11 HTTP library accepts some malformed Chunked-Encoding bodies (CVE-2025-43859). This issue is fixed in version 0.34.2_1 of the affected component. The update also includes an update to the ansible.controller collection to version 4.5.23.
The Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 6.3.0.2. This is due to add_role() and user_role() functions missing proper capability checks performed through the validate_rest_call() function. This makes it possible for unauthenticated attackers to set the role of arbitrary users to administrator granting full access to the site, though privilege escalation requires an active account on the site so this is considered an authenticated privilege escalation.
CVE-2025-1801 is a concurrency vulnerability in the Ansible automation-gateway version 2.5.0. It arises from improper synchronization in handling concurrent gRPC requests, leading to a race condition. This flaw allows a less privileged user to potentially obtain the JWT token of a more privileged user, risking privilege escalation and exposure of confidential data. Red Hat has issued an important security advisory and released patches for Ansible Automation Platform 2.5 to address this issue.
A moderate severity denial-of-service vulnerability (CVE-2024-56374) exists in the ansible-lightspeed-container component of Red Hat Ansible Automation Platform 2.5. This vulnerability relates to IPv6 validation and could potentially allow disruption of service. Red Hat has released updates including Automation Controller 4.6.7, Automation EDA Controller 1.1.4, and Ansible Lightspeed 2.5.20250121 to address this issue. The advisory also includes other configuration improvements unrelated to the vulnerability. The affected products include Red Hat Ansible Automation Platform 2.5 for RHEL 8 and RHEL 9 across multiple architectures. No known exploits in the wild have been reported. Patch status is confirmed with updated component versions provided by Red Hat.
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):
* automation-controller: Jinja has a sandbox breakout through indirect reference to format method (CVE-2024-56326)
* automation-controller: Jinja has a sandbox breakout through malicious filenames (CVE-2024-56201)
* automation-controller: Django: potential denial-of-service vulnerability in IPv6 validation (CVE-2024-56374)
* python3.11-django: potential denial-of-service vulnerability in IPv6 validation (CVE-2024-56374)
* python3.11-django: Potential denial-of-service in django.utils.html.strip_tags() (CVE-2024-53907)
* python3.11-jinja2: Jinja has a sandbox breakout through indirect reference to format method (CVE-2024-56326)
* python3.11-jinja2: Jinja has a sandbox breakout through malicious filenames (CVE-2024-56201)
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 controller
* Fixed an issue where the order of source inventories was not respected by the ansible.controller collection (AAP-38524)
* Fixed an issue where an actively running job on an execution node may have had its folder deleted by a system task (AAP-38137)
* automation-controller has been updated to 4.6.7
Event-Driven Ansible:
* Fixed an issue where users were unable to filter Rule Audits by rulebook activation name (AAP-39253)
* Users are now able to create a new Event-Driven Ansible credential by copying an existing one (AAP-39249)
* Added support for file and env injectors for Credentials (AAP-39091)
* Fixed an issue where the input field of the injector configuration could not be empty (AAP-39086)
* Fixed an issue where the application version in the openapi spec was incorrectly set (AAP-38392)
* Fixed an issue where activations were not properly updated in some scenarios with a high load of the system (AAP-38374)
* automation-eda-controller has been updated to 1.1.4
Container-based Ansible Automation Platform
* Allow user to not provide the Postgresql admin account with external database (AAP-39077)
* Using PostgreSQL TLS certificate authentication with an external database is now available (AAP-38400)
* containerized installer setup has been updated to 2.5-9
RPM-based Ansible Automation Platform
* Fixed an issue where gateway could not be setup with custom SSL certificates (AAP-38985)
* Fixed an issue where the gateway services are not restarted when a dependency changes (AAP-38918)
* Fixed an issue where setting automationedacontroller_max_running_activations could cause the installer to fail (AAP-38708)
* ansible-automation-platform-installer and installer setup have been updated to 2.5-8
Additional changes:
* python3.11-django has been updated to 4.2.18
* python3.11-jinja2 has been updated to 3.1.5
* python3.11-pulpcore has been updated to 3.49.30
Red Hat Ansible Automation Platform 2.4 has multiple security vulnerabilities including denial of service through data corruption in gRPC-C++, potential denial of service in IPv6 validation, Jinja sandbox breakouts via malicious filenames and indirect format method references, and request smuggling in aiohttp due to incorrect chunk extension parsing. These issues affect the ansible-lightspeed-container component and have been addressed in updates to the ansible.controller collection, Automation Controller, and Ansible Lightspeed.
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):
* ansible-core: Unsafe Tagging Bypass via hostvars Object in Ansible-Core (CVE-2024-11079)
* automation-gateway: Improper Scope Handling in OAuth2 Tokens for AAP 2.5 (CVE-2024-11483)
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 UI
* Added support for filtering job templates, jobs, and inventories by labels (AAP-36540)
* Fixed an issue where it was not possible to open a job template after removing the user which created the template (AAP-35820)
* Fixed an issue where the inventory source update failed, and did not allow selection of the inventory file (AAP-35246)
* Fixed an issue where the Login Redirect Override setting was missing and not functioning as expected (AAP-33295)
* Disabled auto complete for secret credential fields (AAP-33188)
* Fixed an issue where users were able to select a credential that required a password when defining a schedule (AAP-32821)
* Fixed the navigation Team -> roles -> eda to the created team role page, where it did not work after adding a new team role.(AAP-31873)
* When configuring an Ansible Remote to sync collections from other servers, a requirements file is only required for syncs from Galaxy, and optional otherwise. Without a requirements file, all collections get synced (AAP-31238)
* Fixed an issue where the job output did not show unless you switched tabs (AAP-31125)
* Fixed an issue where the bulk removal of selected role permissions disappeared when more than 4 permissions were selected (AAP-28030)
Event-Driven Ansible
* Fixed an issue where the project sync would not fail on an empty or unstructured git repository (AAP-35777)
* Fixed an issue in the collection where the activation module failed with a misleading error message if the rulebook, project, decision environment, or organization could not be found (AAP-35360)
* Fixed an issue where rulebook validation import/sync fails when a rulebook has a duplicated rule name (AAP-35164)
* Added validation that a host specified as part of a container registry credential conforms to container registry standards (AAP-34969)
* Fixed an issue where the Event Driven Ansible API allowed a credential’s type to be changed (AAP-34968)
* Fixed an issue where a previously failed project could be accidentally changed to completed after a resync (AAP-34744)
* Fixed an issue where no message was recorded when a project did not contain any rulebooks (AAP-34555)
* Fixed an issue whereby multiple Red Hat Ansible Automation Platform credentials were being attached to activations (AAP-34025)
* Fixed an issue where the url field of the event stream was not updated if EDA_EVENT_STREAM_BASE_URL setting changed (AAP-33819)
* Extended the scope of the log_level and debug settings (AAP-33669)
* Fixed an issue where there was an erroneous dependency on the existence of an organization named Default (AAP-33551)
* A project can now be synced with the Event Driven Ansible collection modules (AAP-32264)
* Fixed an issue where occasionally an activation is reported as running, before it is ready to receive events (AAP-31225)
* Fixed an issue where Enabled options had its own scrollbar on the Rulebook Activation Details page (AAP-31130)
* Added 'purge_log_records' to aap-eda-manage to clean up outdated database records (AAP-30684)
* Fixed an issue where the status of an activation was occasionally inconsistent with the status of the latest instance after a restart (AAP-29755)
* Fixed an issue where the user could not edit auto-generated injector vars while creating Event Driven Ansible custom credentials (AAP-29752)
* Fixed an issue where importing a project from a non-existing branch resulted in the completed state instead of a Failed status (AAP-29144)
* Fixed an issue where in some cases the file_watch source plugin in an Event Driven Ansible collection raised the QueueFull exception (AAP-29139)
* In the Rulebook activation create form, selecting a project is now required before selecting a rulebook (AAP-28082)
* The Create Credentials button is now visible irrespective of whether there are any existing credentials or not (AAP-23707)
* automation-eda-controller has been updated to 1.1.3
* ansible-rulebook has been updated to 1.1.2
Container-based Ansible Automation Platform
* Fixed an issue that allowed Automation controll
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):
* automation-controller: dompurify: XSS vulnerability via prototype pollution (CVE-2024-45801)
* automation-controller: path-to-regexp: Backtracking regular expressions cause ReDoS (CVE-2024-45296)
* ansible-core: Exposure of Sensitive Information in Ansible Vault Files Due to Improper Logging (CVE-2024-8775)
* ansible-core: ansible-core user may read/write unauthorized content (CVE-2024-9902)
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 for automation controller:
* Fix job schedules running at incorrect times when rrule interval was set to HOURLY or MINUTELY (AAP-36573)
* Fixed an issue where sensitive data was displayed in the job output (AAP-35582)
* With this update, you can now save a constructed inventory when verbosity is greater than 2 (AAP-35570)
* Fix bug where unrelated jobs could be marked as a dependency of other jobs (AAP-35310)
* Add support for receiving webhooks from Bitbucket Data Center, and add support for posting build statuses back (AAP-35013)
* Notification List no longer errors when notifications have a missing or null organization field (AAP-34051)
* Fixed an issue where Thycotic secret server credentials form fields were mis-matched (AAP-31236)
* automation-controller has been updated to 4.5.13
Updates and fixes for receptor:
* Fixed an issue that caused a Receptor runtime panic error (AAP-36477)
* receptor has been updated to 1.5.1
Updates and fixes for installer and setup:
* Receptor data directory can now be configured using 'receptor_datadir' variable (AAP-36699)
* Fixed issue where metrics-utility command failed to run after updating Automation controller (AAP-36567)
* Fix issue where the dispatcher service went into FATAL status and failed to process new jobs after a database outage of a few minutes (AAP-36456)
* Fixed an issue that caused incorrect IDs for RBAC in the database following a backup restore (AAP-35311)
* With this update, installer tasks that include CA or key information are obfuscated (AAP-27480)
* installer and setup have been updated to 2.4-8
Note: The 2.4-8 installer can restore a backup created with 2.4-8 or later only. Ensure that you make a backup before and after the upgrade to 2.4-8 or later.