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.
Update(s) and Fix(es):
* Update ansible dev-tools to AAP 2.6
* Add ARM, ppc and s390x architectures
A security researcher has developed an open-source AI-powered autonomous exploitation framework using a 1.7 billion parameter model (Qwen3) that automates reconnaissance, vulnerability analysis, and exploit execution locally without relying on paid APIs. This tool leverages LangGraph's ReAct agents to chain offensive security tasks, potentially lowering the barrier for attackers to conduct complex exploits. Although no specific vulnerabilities or affected software versions are identified, the framework's capability to autonomously discover and exploit vulnerabilities poses a significant risk. There are currently no known exploits in the wild using this tool, but its availability could accelerate the development and deployment of automated attacks. European organizations could face increased threats, especially those with exposed internet-facing assets and legacy or unpatched systems. Mitigation requires proactive vulnerability management, network segmentation, and enhanced monitoring for automated attack patterns. Countries with advanced digital infrastructure and high-value targets, such as Germany, France, the UK, and the Netherlands, are likely to be most affected. Given the potential for remote code execution and full automation without user interaction, the threat severity is assessed as high. Defenders should prioritize detection of AI-driven attack behaviors and invest in threat intelligence to anticipate evolving exploitation techniques.
Red Hat released an update for Ansible Automation Platform 2.6 addressing multiple issues including bug fixes, feature enhancements, and stability improvements. The update fixes errors such as Redis broken pipe in long-running jobs, issues with object storage secrets in backups, and problems with project sync and job templates. It also adds support for IPv6 dual stack by default, improves API accessibility for AI tools, and includes developer preview features like Ansible MCP Server support. The advisory does not describe any specific security vulnerability exploitation or active threats.
Multiple industrial control system (ICS) vulnerabilities have been patched by Siemens, Rockwell Automation, Schneider Electric, and Phoenix Contact. These vulnerabilities affect a variety of ICS/OT products and include issues that could lead to arbitrary code execution, denial of service, unauthorized access, man-in-the-middle attacks, and information disclosure. Siemens addressed critical vulnerabilities in Comos, Sicam T, and Ruggedcom ROX products, as well as high and medium severity issues in other products. Schneider Electric patched vulnerabilities related to Windows Server Update Services and ZombieLoad affecting EcoStruxure Foxboro DCS. Rockwell Automation fixed a high-severity denial of service and SQL injection vulnerabilities. Phoenix Contact addressed multiple vulnerabilities including XSS and authentication issues in its FL SWITCH 2xxx series. These vulnerabilities have been officially patched by the vendors.
n8n is an open source workflow automation platform. Versions 0.123.1 through 1.119.1 do not have adequate protections to prevent RCE through the project's pre-commit hooks. The Add Config operation allows workflows to set arbitrary Git configuration values, including core.hooksPath, which can point to a malicious Git hook that executes arbitrary commands on the n8n host during subsequent Git operations. Exploitation requires the ability to create or modify an n8n workflow using the Git node. This issue is fixed in version 1.119.2. Workarounds include excluding the Git Node (Docs) and avoiding cloning or interacting with untrusted repositories using the Git Node.
A newly reported security concern involves prompt injection attacks within GitHub Actions workflows that utilize AI agents. This threat exploits the way AI-driven automation interprets and executes prompts, potentially allowing attackers to inject malicious instructions. Although no known exploits are currently active in the wild, the medium severity rating reflects the risk of unauthorized command execution and data leakage within CI/CD pipelines. European organizations using GitHub Actions with integrated AI tools are at risk, especially those in software development and critical infrastructure sectors. Mitigation requires careful prompt sanitization, strict workflow permissions, and monitoring of AI interactions within automation. Countries with high GitHub adoption and advanced software ecosystems, such as Germany, the UK, France, and the Netherlands, are most likely to be affected. Given the potential impact on confidentiality and integrity, ease of exploitation via crafted inputs, and the broad use of GitHub Actions, the suggested severity is medium. Defenders should prioritize securing AI prompt inputs and restricting workflow access to mitigate this emerging threat.
Let’s Encrypt, a widely used certificate authority, plans to reduce the validity period of its SSL/TLS certificates from 90 days to 45 days. This change aims to improve security by limiting the window of exposure if a certificate is compromised. While this is not a vulnerability or exploit, it impacts certificate management processes and automation for organizations relying on Let’s Encrypt certificates. European organizations using Let’s Encrypt will need to adjust their renewal workflows to accommodate the shorter validity period. Failure to do so could lead to service disruptions due to expired certificates. The change does not introduce new attack vectors but increases operational demands on IT teams. Countries with high adoption of Let’s Encrypt certificates and strong digital infrastructure are more likely to be affected. This update underscores the importance of robust automation and monitoring in certificate lifecycle management. Overall, this is a security policy change rather than a direct threat or vulnerability.
The U. S. Cybersecurity and Infrastructure Security Agency (CISA) has added a vulnerability affecting OpenPLC ScadaBR to its Known Exploited Vulnerabilities catalog. This flaw pertains to the OpenPLC ScadaBR platform, which is used for industrial control systems and SCADA environments. Although no specific CVSS score or detailed technical exploit information is provided, the vulnerability is assessed as medium severity. There are no known exploits in the wild at this time, and technical discussion and details remain minimal. The vulnerability could potentially impact the confidentiality, integrity, and availability of industrial control systems if exploited. European organizations using OpenPLC ScadaBR, especially in critical infrastructure sectors, should be vigilant. Mitigation should focus on monitoring for updates from vendors, applying patches promptly once available, and implementing network segmentation and access controls. Countries with significant industrial automation and critical infrastructure sectors, such as Germany, France, and the UK, are likely to be most affected.
A security update for the go-rpm-macros package in Red Hat Enterprise Linux 9 addresses a moderate severity vulnerability identified as CVE-2025-47906. The flaw involves the os/exec package's LookPath function returning unexpected paths. This package facilitates build-stage RPM automation for Go language packages. The update is available for multiple architectures and variants of Red Hat Enterprise Linux 9.
The 'Split-Second Side Doors' threat exploits a Time-Of-Check to Time-Of-Use (TOCTOU) vulnerability within CI/CD pipelines by leveraging bot-delegated actions to introduce malicious changes in a narrow time window. This attack undermines the trust model of automated software delivery processes, potentially allowing unauthorized code to be injected without detection. Although no known exploits are currently in the wild, the concept highlights a medium-severity risk to software integrity and supply chain security. European organizations relying heavily on CI/CD automation and bot-driven workflows are at risk, especially those in software development, finance, and critical infrastructure sectors. Mitigation requires enhancing pipeline security by implementing atomic operations, strict bot authentication, real-time monitoring, and immutable build artifacts. Countries with advanced software industries and significant CI/CD adoption, such as Germany, France, and the UK, are most likely to be affected. Given the medium severity, the threat impacts integrity primarily, with moderate exploitation complexity and no known active exploitation. Defenders should prioritize securing CI/CD workflows against TOCTOU race conditions and bot misuse to maintain software supply chain trust.
The Shai-Hulud attack involves a widespread supply chain compromise where over 300 NPM packages and 21,000 GitHub repositories were infected within hours via a fake Bun runtime. This phishing-based attack leverages a malicious runtime impersonation to inject malicious code into popular open-source projects, potentially impacting developers and organizations relying on these packages. Although no known exploits in the wild have been reported yet, the rapid scale and targeting of widely used repositories pose a significant risk to software supply chains. The attack's medium severity reflects the potential for code integrity compromise and downstream impact on applications using these dependencies. European organizations that heavily depend on JavaScript ecosystems and open-source software development are at risk of indirect compromise. Mitigation requires proactive supply chain security measures, including dependency auditing, runtime verification, and enhanced developer awareness to detect and avoid fake runtimes. Countries with strong software development sectors and large tech industries, such as Germany, the UK, France, and the Netherlands, are most likely to be affected. Given the attack vector and scale, the suggested severity is high due to the potential widespread impact on confidentiality, integrity, and availability of software systems without requiring user interaction but exploiting developer trust and automation.
A recent report discusses what is described as the first autonomous AI-driven cyberattack, highlighting the urgent need for changes in SaaS security paradigms. The attack reportedly leverages AI capabilities to conduct operations without human intervention, potentially increasing the speed and scale of exploitation. While technical details remain sparse and no known exploits are currently active in the wild, the emergence of autonomous AI attacks signals a shift in threat actor capabilities. European organizations relying heavily on SaaS platforms may face increased risks due to the automation and sophistication of such attacks. Mitigation requires enhanced monitoring for AI-driven anomalies, integration of AI-aware defense mechanisms, and rigorous SaaS security posture management. Countries with significant SaaS adoption and critical infrastructure reliance on cloud services, such as Germany, the UK, France, and the Netherlands, are likely to be most affected. Given the medium severity assessment and lack of exploitation evidence, the threat is serious but not yet critical. Defenders should prioritize understanding AI threat vectors and adapt security controls accordingly.
A new malware campaign has been discovered on the Python Package Index (PyPI) involving malicious 'spellchecker' packages. These packages contain a heavily obfuscated, multi-layer encrypted backdoor designed to steal cryptocurrency wallets from infected systems. The threat actors leverage the popularity of Python packages to distribute this malware, targeting developers and users who install these packages. Although no known exploits in the wild have been reported yet, the campaign poses a medium-level risk due to the potential financial impact and the stealthy nature of the backdoor. The malware's multi-layer encryption complicates detection and analysis, increasing the risk of prolonged undetected compromise. European organizations using Python environments for development or automation, especially those involved with cryptocurrency, are at risk. Mitigation requires proactive package vetting, enhanced monitoring for suspicious package behavior, and restricting installation of unverified packages. Countries with significant Python developer communities and active cryptocurrency sectors, such as Germany, the UK, France, and the Netherlands, are more likely to be affected. Given the threat's impact on confidentiality and the ease of exploitation via package installation, the suggested severity is medium.
This threat analysis highlights how certain legitimate Python packages can be repurposed by attackers to build surveillance and spyware tools. These packages enable capabilities such as keylogging, screen capture, webcam access, and browser data extraction. The write-up emphasizes the ease with which these libraries can be misused to create full-scope monitoring malware without requiring vulnerabilities in the packages themselves. While no direct exploits or vulnerabilities are reported, the potential for abuse exists due to the functionality these packages provide. The threat is categorized as medium severity given the potential impact on confidentiality and privacy, combined with the ease of misuse by attackers. European organizations using Python in development or automation environments could be targeted for espionage or data theft. Mitigations focus on developer awareness, supply chain security, and monitoring for suspicious use of these packages. Countries with strong software development sectors and critical infrastructure relying on Python are most likely to be affected. This analysis is based on a recent audit-style report shared on Reddit’s NetSec community and does not describe an active exploit campaign.
The EchoGram flaw is a recently disclosed vulnerability that allows attackers to bypass guardrails implemented in major large language models (LLMs). This bypass enables the LLMs to generate outputs that would normally be restricted by safety and content moderation filters. Although no known exploits are currently in the wild, the flaw poses a medium-level risk due to its potential to facilitate malicious use of LLMs. The vulnerability does not have detailed technical disclosures or patch information yet, limiting immediate mitigation options. European organizations using LLMs for customer interaction, content generation, or automation could face risks related to misinformation, policy violations, or reputational damage. Countries with high adoption of AI technologies and strict regulatory environments are particularly at risk. Mitigation should focus on enhanced monitoring of LLM outputs, restricting sensitive use cases, and collaborating with vendors for updates. Given the medium severity, the threat requires attention but is not immediately critical. Defenders should prioritize awareness and prepare for potential future exploits as more details emerge.
A high-priority cyber espionage campaign has been reported involving Chinese threat actors leveraging Anthropic's AI technology to automate their operations. This campaign represents an evolution in threat actor capabilities by integrating advanced AI to enhance attack automation and sophistication. Although no specific vulnerabilities or exploits are detailed, the use of AI suggests increased speed, scale, and adaptability in targeting. European organizations, especially those in critical infrastructure, government, and technology sectors, face heightened risks due to potential espionage and data exfiltration. Mitigation requires tailored defenses including AI threat detection, enhanced monitoring for automated attack patterns, and strict access controls. Countries with significant technological and industrial assets, such as Germany, France, and the UK, are likely primary targets. Given the campaign nature, lack of authentication requirements, and potential broad impact, the threat severity is assessed as high. Defenders should prioritize intelligence sharing and proactive AI-driven security measures to counter this emerging threat.
Cisco has identified that open-weight AI models are vulnerable to exploitation during long conversations, allowing attackers to manipulate the AI's behavior. This vulnerability arises because extended interaction sequences can be crafted to bypass safety or operational constraints embedded in the AI models. Although no known exploits are currently active in the wild, the potential for misuse is significant, especially in environments relying on these AI models for decision-making or automation. The threat primarily affects organizations deploying open-weight AI models without robust monitoring or input validation. European organizations using such AI technologies in customer service, automation, or security contexts may face risks of data leakage, misinformation, or operational disruption. Mitigation requires implementing strict conversation length limits, input sanitization, and continuous monitoring of AI outputs for anomalous behavior. Countries with advanced AI adoption and critical infrastructure relying on AI, such as Germany, France, and the UK, are most likely to be impacted. Given the ease of exploitation through crafted conversations and the high impact on confidentiality and integrity, the severity is assessed as high.
Nine malicious NuGet packages have been identified that contain time-delayed payloads designed to disrupt databases and industrial systems. These packages, once integrated into software projects, activate their payloads after a delay, complicating detection and mitigation efforts. Although no known exploits are currently active in the wild, the threat poses a medium severity risk due to its potential to impact critical infrastructure and data integrity. European organizations relying on NuGet packages in software development, especially those in industrial automation and database management sectors, should be vigilant. The delayed activation mechanism increases the risk of prolonged undetected presence, potentially causing significant operational disruption. Mitigation requires proactive package auditing, supply chain security enhancements, and monitoring for unusual system behaviors. Countries with strong industrial bases and extensive software development ecosystems, such as Germany, France, and the UK, are particularly at risk. Given the complexity and potential impact, the threat is assessed as medium severity. Immediate attention to supply chain security hygiene is recommended to prevent exploitation.
Multiple cross-site scripting (XSS) vulnerabilities have been identified in IBM Business Automation Workflow. These vulnerabilities could allow attackers to inject malicious scripts into the application. A fixed version 25.0.0-IF002 is available addressing these issues.