Threat database

Incus before 6.0.7, 6.1.0 before 7.0.2, and 7.1.0 before 7.5.0 contains an arbitrary file write vulnerability in sftpRecursivePullFile that allows a malicious incus-agent to escape the target directory during incus file pull -r. Attackers with root in a virtual machine can return duplicate entries reported first as symlinks then as files or directories, writing attacker-controlled files such as /etc/shadow on the operator's host.

CVE-2026-115377 is a critical arbitrary file write vulnerability in the Incus container management software (lxc). It affects versions before 6.0.7, versions from 6.1.0 up to but not including 7.0.2, and versions from 7.1.0 up to but not including 7.5.0. The flaw allows malicious migration sources to write files on the host system by planting symbolic links in transferred volumes during migration. This can lead to full host compromise if exploited.

Incus versions 7.0.1 before 7.0.2 and 7.2.0 before 7.5.0 contain an authorization bypass vulnerability. This flaw allows project-restricted clients to copy volumes by omitting the source.type parameter. Attackers can exploit this by sending crafted POST requests to the custom volumes endpoint with a chosen source.project, enabling them to copy and read volumes, snapshots, and configurations from other projects.

Incus versions 7.0.0 before 7.0.2 and 7.1.0 before 7.5.0 contain a path traversal vulnerability that allows clients with instance creation privileges to write files on the host system. The vulnerability arises from unvalidated custom volume names in instance backup index.yaml files, which can include '../' sequences. Exploiting this flaw enables attackers to create root-owned directories with attacker-controlled content, potentially leading to full host compromise.

Incus 7.0.0 before 7.0.2 and 7.1.0 before 7.5.0 contains a signature verification flaw in its built-in S3 server that allows presigned URL holders to inject unsigned x-amz-* headers. Attackers can add an unsigned X-Amz-Copy-Source header to a presigned upload URL to copy other bucket objects onto the granted key, disclosing their contents and ETags.

Incus versions before 6.0.7, versions from 6.1.0 up to but not including 7.0.2, and versions from 7.1.0 up to but not including 7.5.0 contain a missing authorization vulnerability in the GET /1.0/operations/{uuid} endpoint. This flaw allows project-restricted clients to access operations belonging to other projects. Exploitation requires possession of a restricted certificate and knowledge of a valid operation UUID. Successful exploitation can expose sensitive data including command lines, environment secrets, websocket secrets, and trust enrolment tokens.

CVE-2026-115372 is a critical vulnerability in Incus versions 7.3.0 up to but not including 7.5.0. It allows restricted project users to bypass project restrictions by setting block.create_options during volume update, copy, and move operations. This can lead to argument injection into the mkfs command executed as root, potentially allowing privilege escalation.

Incus versions 6.0.3 before 6.0.7, 6.6.0 before 7.0.2, and 7.1.0 before 7.5.0 contain an improper authorization vulnerability that allows restricted TLS clients to access storage bucket keys in the default project. This vulnerability enables attackers to retrieve S3 access and secret keys, potentially allowing them to read, modify, or delete objects in those buckets.

Incus 6.0.5 before 6.0.7, 6.12.0 before 7.0.2, and 7.1.0 before 7.5.0 contains a restriction bypass vulnerability that allows restricted project users to use pull mode migration via clustered refresh requests. Attackers with instance creation rights can send a refresh migration request for an existing instance to make the server open outbound TLS websocket connections and probe reachable services.

Mistune versions before 3.3.0 have a path traversal vulnerability in the Include directive that allows attackers to read arbitrary files by using ../ sequences. Additionally, attackers can inject HTML via unescaped error messages and included file contents, enabling cross-site scripting even when escape=True is set. This vulnerability has a high severity rating with a CVSS score of 8.7.

CVE-2026-114519 is a missing authorization vulnerability in Roskus Prospero Flow CRM versions from 2.0.0 up to but not including 5.26.0. It allows users with a basic role to read account details of other users within their company and, from version 3.5.0 onward, to delete those accounts. The vulnerability arises because the API routes for reading and deleting users only validate the JSON Web Token but do not enforce permission checks. Notably, users in the default company can delete any account across companies. This can lead to unauthorized access to personal data and deletion of accounts, including administrative ones.

Mistune versions before 3.3.0 have a path traversal vulnerability in the opt-in Include directive. This flaw allows attackers to read arbitrary local files by providing relative or absolute paths. Exploitation can lead to disclosure of sensitive files such as /etc/passwd and injection of unescaped HTML or script content into rendered Markdown output.

Mistune versions before 3.3.0 contain a critical path traversal vulnerability in the RST include directive. This flaw allows attackers to read arbitrary files by using relative or absolute paths in markdown include directives. Exploitation can lead to exposure of sensitive files such as credentials or environment data embedded in rendered HTML.

Mistune before 3.3.0 contains an algorithmic complexity vulnerability in the inline link parser that allows unauthenticated attackers to exhaust CPU by submitting long runs of unmatched '[' characters. Attackers can send small markdown payloads that trigger O(N^2) parse_link_text and parse_link_label probing, occupying rendering workers for 30+ seconds per 16 KB input.

Mistune versions from 3.2.1 up to but not including 3.3.0 contain a CSS injection vulnerability via the unvalidated figwidth option in the figure directive. This allows attackers controlling markdown input to inject arbitrary CSS style declarations, potentially causing victim browsers to send requests to attacker-controlled servers and leak attribute values. The vulnerability has a medium severity with a CVSS 4.0 score of 5.3.

Mistune versions before 3.3.0 have a cross-site scripting (XSS) vulnerability in the Include directive. This directive emits included HTML content as raw block_html tokens without proper neutralization. An attacker who can place a readable HTML file on the system can exploit this by referencing it with an include directive combined with path traversal, leading to stored script execution when escape=False is set.

Mistune versions 3.0.0 up to but not including 3.3.0 contain a denial of service vulnerability caused by inefficient regular expression handling in the parse_link_text function. This flaw allows attackers to craft markdown input with deeply nested square brackets, triggering quadratic parsing time and potentially exhausting server CPU resources.

Mistune from 3.0.0 before 3.3.0 contains an algorithmic complexity vulnerability in the inline link parser's parse_link_text function that allows unauthenticated attackers to exhaust CPU with unbalanced brackets. Attackers can submit Markdown containing many unbalanced '[' or '![' characters, forcing repeated unbounded forward scans and tying up worker processes for minutes.

Mistune versions before 3.3.0 have an inefficient algorithmic complexity vulnerability in the parse_link_text function. This flaw allows remote attackers to cause denial of service by submitting markdown with long runs of unmatched square brackets. The vulnerability triggers repeated forward scans that stall worker processes for minutes, leading to service disruption.

In September 2026, an SEO poisoning campaign distributed Armorsteal malware via fake websites impersonating Chocolatey and Microsoft Activation Scripts tools. The malware is Python-based, protected by Pyarmor, and includes modules for remote access, surveillance, and information stealing. It captures keystrokes, clipboard data, cryptocurrency wallets, browser data, Discord tokens, passwords, and SSH keys. The campaign uses anti-analysis techniques such as cloud provider detection and code obfuscation, with frequent infrastructure changes observed. No patch or remediation is indicated, and no known exploits in the wild are reported.