Three new high-severity local privilege escalation (LPE) vulnerabilities affecting Linux were recently disclosed, creating significant global risk. Although user-level access is a prerequisite for their exploitation, the new CVEs allow command execution as the root user and full system takeover. The CVEs are considered reliably exploitable on all major Linux distributions.

The name “Copy Fail” was given to CVE-2026-31431 (CVSS 7.8) at disclosure time, and subsequent investigations led to the discovery of CVE-2026-43284 (CVSS 8.8), dubbed “Copy Fail 2”, and CVE-2026-43500 (CVSS 7.8). The attack chain involving CVE-2026-43284 and CVE-2026-43500 was dubbed “Dirty Frag”. CVE-2026-31431 has been added to CISA’s KEV list, after active exploitation was reported by Microsoft. Microsoft also considers Dirty Frag high-risk for post-exploitation activity. Numerous national CERT alerts have been issued globally for the CVEs [1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21][22].

CVE-2025-20393-cisco-spam-filter

Greenbone provides Linux package-level detection for all three emergency CVEs mentioned above across a wide spectrum of Linux distributions [1][2][3]. Greenbone’s coverage also extends to security updates for a wide array of software and hardware products. As a result, OPENVAS SCAN can also help identify the impact of Copy Fail, Copy Fail 2, and Dirty Frag in third-party Linux-based products.

Greenbone’s OPENVAS SCAN has industry-leading detection for many Linux distributions with authenticated Local Security Checks (LSC). Authenticated LSCs provide reliable detection because they analyze endpoint systems from within, build asset inventories, uncover package-level software vulnerabilities, and identify other security misconfigurations.

Start Your Free Trial

With continuously updated vulnerability detection, risk prioritization intelligence, and scalable operations, OPENVAS SCAN helps organizations strengthen their cybersecurity posture by reducing exposure to known threats across IT environments.

Start evaluating Greenbone’s flagship product, OPENVAS SCAN. Our entry level enterprise appliance, OPENVAS BASIC, is available for free and includes a two week trial of the OPENVAS ENTERPRISE FEED.

 

What Are Copy Fail, Copy Fail 2, and Dirty Frag?

The disclosure timeline for Copy Fail, Copy Fail 2, and Dirty Frag moved quickly, overlapping with mainline Linux kernel patching and downstream Linux distribution updates. Because several related events occurred within a short period, it is useful to first clarify the terminology and timeline of events:

  • Copy Fail: Refers to CVE-2026-31431 (CVSS 7.8), an LPE flaw in the Linux kernel. Copy Fail was privately reported on March 23rd, 2026, and patched in the mainline Linux kernel on April 1st. On April 22nd, the flaw was published as CVE-2026-31431, and a full technical write-up [1] and proof-of-concept (PoC) exploit [2] followed days later. Microsoft reported active exploitation on May 1st, 2026 and CISA added CVE-2026-31431 to the Known Exploited Vulnerabilities (KEV) catalog the same day. Since then, additional technical write-ups [3][4][5], PoC exploits [5][6], and a commercial penetration testing exploit [7] have become available.
  • Copy Fail 2: Refers to CVE-2026-43284 (CVSS 8.8), published on May 8th, 2026. The flaw was discovered during follow-on research into the root cause of Copy Fail. Copy Fail 2 was privately reported on April 30th, 2026, and the fix was merged into the mainline Linux kernel on May 8th. A technical description [8] and PoC exploit [9] were published on May 7th, one day before upstream kernel patches became available to downstream Linux distributions. The original technical write-up indicates that the underlying flaw could be exploited alone for root-level access, without being chained with other software flaws, such as in Dirty Frag described below.
  • Dirty Frag: Refers to the chained exploitation of CVE-2026-43284 (Copy Fail 2) and CVE-2026-43500 (CVSS 7.8). Although CVE-2026-43500 was responsibly disclosed and published on May 11th, 2026, sensitive information became publicly available before a fix was committed to the mainline Linux kernel. This prompted security researcher Hyunwoo Kim (@v4bel) to release technical details [9] and PoC code [10] on May 8th, before the root cause of CVE-2026-43500 was patched in the mainline Linux kernel on May 10th, 2026.

A Global Risk Analysis of Copy Fail, Copy Fail 2, and Dirty Frag

The global cyber security risk posed by Copy Fail, Copy Fail 2, and Dirty Frag is high. Linux is widely used in network and security appliances, workstations, cloud environments, Internet of Things (IoT) devices, embedded systems, industrial environments, and critical infrastructure. All three CVEs are considered highly reliable and affect every major Linux distribution, creating broad global exposure. The vulnerabilities have been traced back to three separate upstream Linux commits; Copy Fail [72548b093ee3] and Copy Fail 2 [cac2661c53f3] were introduced in 2017, while the Dirty Frag commit [2dc334f1a63a] was introduced in 2023 [1][2].

Active exploitation of CVE-2026-31431 (Copy Fail) has been observed by Microsoft and added to CISA’s KEV list, although few details about the attacks are available. Microsoft also considers Dirty Frag high risk for post-exploitation activity.  The immediate risk landscape is further compounded by the fast-paced nature of events. Sensitive technical information and exploit code for CVE-2026-43284 and CVE-2026-43500 were disclosed before patches reached downstream Linux distributions, increasing the window of opportunity for attackers. Although security researchers followed responsible disclosure paths, sensitive details about CVE-2026-43284 were released in parallel with upstream patch commits to the Linux kernel. For CVE-2026-43500, early public exposure came from a patch submitted to the public netdev mailing list on April 29th.

Complete technical details and PoC exploit code are publicly available for all three CVEs, increasing the risk of exploitation by low-skilled attackers and initial access brokers (IAB) who sell unauthorized access to cyber-criminal organizations. Numerous national CERT alerts have been issued globally, and numerous product vendors have issued advisories and emergency patches to address the issues [3][4][5][6][7][8][9][10][11][12][13].

Although LPE flaws require local account access for exploitation, attackers can gain the required access in many ways, such as:

  • Existing software vulnerabilities [T1190] [T1203]
  • Using stolen credentials [T1078]
  • Phishing and spear phishing [T1566]
  • Malicious insiders [T1199]
  • Supply chain compromise [T1195]

Potential impacts of successful exploitation include:

  • Ransomware attacks [T1486]
  • Credential theft [TA0006]
  • Rootkit deployment [T1014] for covert, persistent access [TA0003]
  • Binary replacement [T1554]
  • Disabling security tools [TA0005]
  • Botnet enrollment [T1584.005]
  • Lateral movement to other systems [TA0008]
  • Dropping poisoned files [T1204.002]
  • Downstream supply-chain attacks [T1195]

Mitigating Copy Fail, Copy Fail 2, and Dirty Frag

As of May 13th, patches are still not available for all aforementioned CVEs across all major Linux distributions. Full mitigation requires identifying affected systems and installing operating system patches as soon as possible. As a temporary workaround, defenders can disable the vulnerable algif_aead, esp6, esp4, and rxrpc kernel modules [1][2][3][4]. However, in some cases this approach could be problematic if the modules support required functionality.

Due to active exploitation and the availability of PoC exploits, defenders should consider monitoring for indicators of compromise (IoCs) and suspicious activity, and conduct incident response if a breach is suspected.

It’s also important to remember that Copy Fail, Copy Fail 2, and Dirty Frag may introduce additional risk to many third-party products that use Linux. Defenders should scan all infrastructure for vulnerabilities and follow the affected product vendor’s security guidance.

Greenbone provides Linux package-level detection for all three emergency CVEs mentioned above across a wide spectrum of Linux distributions [5][6][7]. Greenbone’s coverage also extends to security updates for a wide array of software and hardware products, meaning that OPENVAS SCAN can help identify the impact of Copy Fail, Copy Fail 2, and Dirty Frag in third-party Linux-based products as well.

Greenbone’s OPENVAS SCAN has industry-leading detection for many Linux distributions with authenticated Local Security Checks (LSC). Authenticated LSCs provide reliable detection because they analyze endpoint systems from within, build asset inventories, uncover package-level software vulnerabilities, and identify other security misconfigurations.

 

Start Your Free Trial

With continuously updated vulnerability detection, risk prioritization intelligence, and scalable operations, OPENVAS SCAN helps organizations strengthen their cybersecurity posture by reducing exposure to known threats across IT environments.

Start evaluating Greenbone’s flagship product, OPENVAS SCAN. Our entry level enterprise appliance, OPENVAS BASIC, is available for free and includes a two week trial of the OPENVAS ENTERPRISE FEED.

 

Summary

Copy Fail, Copy Fail 2, and Dirty Frag create a serious risk to any systems or devices that use Linux. The flaws are all local privilege escalation (LPE) vulnerabilities that require user-level access to exploit. However, risk is increased due to reliable exploitation on all major Linux distributions, the availability of public PoC exploit code, and in the case of CVE-2026-31431, known active exploitation.

Organizations should regularly scan their IT infrastructure with OPENVAS SCAN to ensure Linux kernel patches are applied network-wide and vulnerable third-party software and hardware are identified. Security updates should be installed as soon as they become available. Temporary kernel module workarounds may be considered in the meantime where feasible. Additional security concerns include restricting local access paths, and monitoring systems for indicators of compromise (IoCs).

In April 2026, the cyber security landscape was flooded with news about Anthropic’s new Mythos bug-hunting AI and Project Glasswing. The rose-colored takeaway is that one year from now, software will be free from vulnerabilities because AI will find all of the flaws and vendors will patch. Major software companies will scan all their products pre-release and software vulnerabilities will be a thing of the past. However, reality likely has something else in store. Let’s dig into the evolving cyber risk landscape of April 2026.

CVE-2025-20393-cisco-spam-filter

Although several of this month’s top threats are mentioned here, many emerging vulnerabilities are not. OPENVAS SCAN doesn’t just detect the most critical flaws in your IT environment. Greenbone’s OPENVAS ENTERPRISE FEED adds thousands of new vulnerability tests per month to detect flaws in enterprise software applications, IT networking products, major OSs and browsers, Linux packages, productivity tools, agentic AI tooling, and more. Defenders seeking to detect and protect can try Greenbone’s entry-level OPENVAS BASIC for free, including a two-week trial of the ENTERPRISE FEED.

Start Your Free Trial

With continuously updated vulnerability detection, risk prioritization intelligence, and scalable operations, OPENVAS SCAN helps organizations strengthen their cybersecurity posture by reducing exposure to known threats across IT environments.

Start evaluating Greenbone’s flagship product, OPENVAS SCAN. Our entry level enterprise appliance, OPENVAS BASIC, is available for free and includes a two week trial of the OPENVAS ENTERPRISE FEED.

 

Mythos or Reality? Time to Find Out

Project Glasswing created a media frenzy, yet transparency remained elusive. Anthropic did not release a public list matching its claim of “thousands of zero-day vulnerabilities” across “every major operating system” and “every major web browser”. This month, VulnCheck found only 75 published CVE records mentioning “Anthropic” and only 40 of those were credited to Anthropic researchers. So far, only one CVE is explicitly attributed to Project Glasswing: CVE-2026-4747 (CVSS 8.8).

The potential risk posed by offensive AI technology is high. The immediate advice from established cyber security authorities SANS Institute and the Cloud Security Alliance (CSA) is for organizations to double down on core cybersecurity measures. Ensure strong mitigating and preventative controls such as the principle of least privilege (PoLP), network segmentation to prevent lateral movement, patch faster, and be prepared for a possible influx of new high-severity CVEs. Also, where potential zero-day exploitation creates high risk, outfit endpoints with detection and response technologies, and be prepared to redeploy critical assets with minimal downtime. Third-party risk can also directly impact your organization’s operations. This is a more balanced interpretation of the near-term risk that organizations face.

Apache ActiveMQ Actively Exploited for RCE

CVE-2026-34197 (CVSS 8.8, EPSS ≥ 98th pctl) is a code injection flaw caused by improper input validation affecting Apache ActiveMQ Classic. Apache ActiveMQ is a popular Java-based message broker that handles asynchronous communication via message queues with support for flexible client options. CVE-2026-34197 has been added to CISA’s Known Exploited Vulnerabilities (KEV) catalog and multiple national CERT agencies have issued alerts globally [1][2][3][4][5][6][7][8]. Previous flaws in ActiveMQ are known to be leveraged in ransomware attacks. A full technical description and proof-of-concept (PoC) exploit kit are publicly available increasing the risk. Shadowserver reports roughly 8,000 exposed instances of ActiveMQ on the Internet.

The new CVE is considered a bypass of CVE-2022-41678 (CVSS 8.8). Exploiting CVE-2026-34197 does not require credentials on ActiveMQ v6.0.0–6.1.1 due to another unpatched missing authentication vulnerability, CVE-2024-32114 (CVSS 8.8). While authentication is required for exploiting other versions of ActiveMQ, default credentials are also a factor for unauthorized access. Incidentally, the Horizon3.ai security researcher who discovered CVE-2026-34197 attributed 80% of the process to a pre-Mythos version of Claude AI.

Greenbone’s OPENVAS ENTERPRISE FEED includes an active check and a remote banner version check for CVE-2026-34197. Users must upgrade to v5.19.4 or v6.2.3 for mitigation.

Trojan Documents Exploiting Adobe Acrobat and Reader

CVE-2026-34621 (CVSS 8.6, EPSS ≥ 92nd pctl) is a prototype pollution flaw [CWE-1321] that allows arbitrary code execution in the context of the current user. CVE-2026-34621 is exploitable via social engineering and requires a malicious PDF file to be opened. CVE-2026-34621 has been added to CISA’s KEV list and Adobe acknowledged active exploitation in a security bulletin. Numerous national CERT alerts have been issued globally [1][2][3][4][5][6][7][8][9][10][11][12][13][14].

According to security researchers, the flaw has been exploited since at least late 2025 as indicated by VirusTotal findings. The identified malware base64-decodes a payload and executes it as JavaScript to extract information from the victim’s computer, including the contents of local files, sends the data to the attacker’s command-and-control (C2) server, and awaits further instructions to execute. Another malware analysis report found that malware exploiting CVE-2026-34621 abuses multiple undocumented internal APIs in Adobe Acrobat and Reader in the attack chain.

Affected products are Acrobat DC Continuous 26.001.21367 and earlier, Acrobat Reader DC Continuous 26.001.21367 and earlier, and Acrobat 2024 Classic 2024 24.001.30356 and earlier on Windows and macOS. The OPENVAS ENTERPRISE FEED includes detection tests for all affected products on Windows [15][16][17] and macOS [18][19][20]. Users should update to a patched version immediately.

CVE-2026-3854: Authenticated RCE in Git Enterprise and GitHub.com

CVE-2026-3854 (CVSS 8.8) allows an authenticated attacker with push permissions to a repository to achieve RCE on a Git server. During a git push operation, user-supplied values are not properly sanitized before being included in internal service headers, potentially resulting in command injection [CWE-77] and RCE.

Several Git products including GitHub.com, GitHub Enterprise Server, and GitHub Enterprise Cloud are affected. A full technical description has been published and public PoC exploits have been sighted by CIRCL.lu. Although GitHub.com’s public infrastructure was affected, internal forensic review found no evidence of in-the-wild exploitation or indicators of compromise (IoC).

The OPENVAS ENTERPRISE FEED includes package-level detection for GitHub Enterprise Server. Users should upgrade to GitHub Enterprise Server versions 3.14.25, 3.15.20, 3.16.16, 3.17.13, 3.18.7, or 3.19.4.

Patch Now! High-Severity Flaws in Core Linux Components

Let’s turn our focus to Greenbone’s support for Linux security advisories and what the OPENVAS ENTERPRISE FEED can do for security teams managing Linux assets by reviewing some of the top Linux flaws from April 2026.

Pack2TheRoot: Linux Privilege Escalation via Linux PackageKit

PackageKit is the D-Bus system-level API for managing software packages across different Linux package managers, including APT, DNF, RPM, and Pacman. CVE-2026-41651 (CVSS 8.8), dubbed Pack2TheRoot, is an attack chain that combines three separate bugs into an exploitable time-of-check-time-of-use (TOCTOU) race condition [CWE-367]. The flaw ultimately allows unprivileged users to install arbitrary packages as root.

Telekom Security published a technical description, including a detailed PoC exploit. Other PoC exploits can also be found online [1][2] and several national CERT alerts have been issued globally [1][2][3]. The OPENVAS ENTERPRISE FEED includes detection for CVE-2026-41651 as reported in Linux security advisories. PackageKit versions 1.0.2 through 1.3.4 are affected and users should update to version 1.3.5.

CVE-2026-33413: Authentication Bypass in etcd

etcd is a distributed key-value store designed for authoritative data coordination in Linux environments. CVE-2026-33413 (CVSS 8.8) is a missing authorization vulnerability [CWE-862] in etcd clusters with auth enabled. The flaw allows attackers to access sensitive etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients. RCE is not described as a potential impact of CVE-2026-33413. However, an attacker may learn cluster topology, including member IDs and advertised endpoints, permanently remove historical revisions, disrupt watch, audit, and recovery workflows, or trigger denial of service (DoS) conditions.

etcd is often associated with Kubernetes, where it stores the cluster’s authoritative state, including nodes, pods, secrets, and control-plane metadata. However, since Kubernetes does not rely on etcd’s built-in authentication and authorization, typical Kubernetes deployments are not affected.

Germany [1] and France [2] have issued national CERT advisories for the flaw. Greenbone includes remote banner version check for detecting exposed etcd services affected by CVE-2026-33413. etcd versions 3.4.42, 3.5.28, and 3.6.9 contain a patch for CVE-2026-33413.

CVE-2026-34714: Trojan Vim Files Can Execute Arbitrary Code

CVE-2026-34714 (CVSS 8.6) allows arbitrary OS commands to be executed when a user opens a specially crafted file. These commands are executed with the privileges of the user who opened the file. CVE-2026-34714 is classified as a command injection flaw caused by improper neutralization of special elements [CWE-78].

There is no public PoC exploit for CVE-2026-34714, and it is not considered exploited in the wild. The OPENVAS ENTERPRISE FEED includes detection for CVE-2026-34714 as reported in Linux security advisories. The flaw was introduced in v9.1.1390 and patched in v9.2.0172.

CVE-2026-34078: Sandbox Escape and RCE via Malicious Flatpak Apps

CVE-2026-34078 (CVSS 10) is a complete sandbox escape of the flatpak run process caused by an exploitable TOCTOU race condition [CWE-367] when file paths provided as sandbox-expose options are replaced with symlinks post-verification. Once flatpak run mounts the swapped-out symlink in the sandbox, a malicious app can read and write arbitrary files on the host and exploit these unauthorized privileges to gain code execution.

There is no public PoC exploit for CVE-2026-34078, and it is not considered exploited in the wild. The OPENVAS ENTERPRISE FEED includes detection for CVE-2026-34078 as reported in Linux security advisories. Users should upgrade to Flatpak version 1.16.4 for mitigation.

Microsoft Risk: New Active Exploitation and Disclosure Controversy

A large Patch Tuesday included 173 new vulnerabilities in Microsoft’s core products. Nineteen were rated as “Exploitation More Likely”, and two were quickly added to CISA’s KEV list. Another critical flaw, CVE-2026-40372 (CVSS 9.1), was disclosed out-of-band. Also, a disgruntled security researcher abandoned the responsible disclosure process with Microsoft and published PoC exploit code for an otherwise undisclosed and unpatched vulnerability.

Let’s review some of these new high-risk Microsoft vulnerabilities:

  • CVE-2026-33825 (CVSS 7.8, EPSS ≥ 87th pctl): A local privilege escalation (LPE) in Microsoft Defender allows a local user to gain SYSTEM-level permissions. Dubbed “BlueHammer”, the flaw was reportedly disclosed by a disgruntled security researcher, along with a PoC exploit. Technical analyses have also been published [1][2]. BlueHammer is exploited in the wild and has been added to CISA’s KEV list. Two additional zero-days disclosed by the disgruntled researcher, dubbed RedSun and UnDefend, remain unpatched by Microsoft despite having PoC exploits [3][4] and being observed in active attacks.
  • CVE-2026-32201 (CVSS 6.5): A new actively exploited flaw in Microsoft SharePoint Server caused by improper input validation [CWE-20] allows an unauthorized attacker to perform spoofing over a network. Technical details about CVE-2026-32201 are not publicly available, and no public PoC exploit exists. Previous SharePoint flaws have been targeted by sophisticated nation-state threat actors [5][6][7]. CVE-2026-32201 comes soon after another SharePoint vulnerability, CVE-2026-20963 (CVSS 9.8, EPSS ≥ 90th pctl), was added to CISA’s KEV in April 2026.
  • CVE-2026-32202 (CVSS 4.3, EPSS ≥ 92nd pctl): A protection mechanism failure [CWE-693] in Windows Shell allows an unauthorized attacker to remotely bypass Microsoft Defender security controls. The flaw has been added to CISA’s KEV list. A detailed technical report from Akamai shows that CVE-2026-32202 is an incomplete patch for CVE-2026-21510 (CVSS 8.8), which was actively exploited by APT-28.
  • CVE-2026-40372 (CVSS 9.1): Changes introduced in version 10.0.6 of the AspNetCore.DataProtection package in .NET Core caused secret decryption failure for some users [8][9]. Following investigation, Microsoft determined that the update also allows unauthorized attackers to elevate privileges over a network. Technical details about CVE-2026-40372 are not publicly available, and no public PoC exploit exists. Versions 10.0.0 – 10.0.6 are affected by CVE-2026-40372 and users should update .NET Core runtime to version 10.0.7 and .NET Core SDK to version 10.0.107 or 10.0.203.

Greenbone’s OPENVAS ENTERPRISE FEED includes detection for all Microsoft CVEs referenced above and frequently updated dedicated families of detection tests for Microsoft products.

CVE-2026-2699: Unauthenticated RCE in Progress ShareFile with Public PoC

CVE-2026-2699 (CVSS 9.8, EPSS ≥ 96th pctl) allows unauthenticated read and write access to restricted configuration pages on Progress ShareFile Storage Controller. The flaw allows changing system configurations and potentially, unauthenticated RCE. CVE-2026-2701 (CVSS 8.8, EPSS ≥ 70th pctl) has a similar impact for authenticated users; an authenticated attacker can upload a malicious file and execute it, leading to RCE.

Progress Software’s products have frequently been targeted in ransomware attacks in the past [1][2][3][4]. Although neither CVE is considered actively exploited yet, watchTowr Labs released a full technical write-up covering both CVEs that includes PoC exploit code. ShadowServer data indicates that the majority of publicly exposed instances are concentrated in the United States. Italy [5] and France [6] have issued CERT alerts for the pair of new CVEs.

The OPENVAS ENTERPRISE FEED includes a remote exploitability check for CVE-2026-2699 and a remote banner version check that covers both CVE-2026-2699 and CVE-2026-2701. All versions of Progress ShareFile StorageZones Controller before 5.12.4 are affected.

CVE-2025-59528: Actively Exploited CVSS 10 Flaw in Flowise

CVE-2025-59528 (CVSS 10, EPSS ≥ 99th pctl) is a code injection flaw [CWE-94] affecting Flowise prior to version 3.0.6. User-defined configuration settings from the CustomMCP node are passed directly to the Function() constructor, which executes JavaScript expressions without security validation. CustomMCP runs with Node.js runtime privileges and has access to dangerous modules such as child_process and fs.

CVE-2025-59528 was disclosed in September 2025, but the flaw gained more attention [1][2][3] this month, when it was reported as actively exploited. Notably, PoC exploit code was revealed by the vendor at disclosure time. The OPENVAS ENTERPRISE FEED has included a remote banner version check for CVE-2025-59528 since it was published, along with numerous tests for other Flowise CVEs, and a product detection module for Flowise. Users should upgrade to version 3.0.6.

Authenticated Command Execution on Juniper Networks MX Series Devices

CVE-2026-33785 (CVSS 8.8) allows a local, authenticated user with low privileges to execute dangerous commands on the CLI on Juniper Networks Junos OS on MX Series. Exploitation could lead to complete system compromise of managed devices. The root cause is missing authorization [CWE-862] for request csds operations, which are only meant to be executed by high-privileged users.

CVE-2026-33785 is not considered actively exploited and PoC exploit code is not publicly available. The OPENVAS ENTERPRISE FEED includes a remote banner version check for CVE-2026-33785, and detection for many other flaws in Juniper Networks products. CVE-2026-33785 affects Junos OS on MX Series, 24.4 releases before 24.4R2-S3 and 25.2 releases before 25.2R2. This issue does not affect Junos OS releases before 24.4.

TrueChaos: Campaign Targeting TrueConf Client in Southeast Asia

CVE-2026-3502 (CVSS 7.8, EPSS ≥ 85th pctl) allows an attacker who can influence the update delivery path to TrueConf Client applications to inject and execute a tampered update payload. TrueConf is a video conferencing and unified communications product family often deployed on-premises in private networks for secure, sovereign communication.

CVE-2026-3502 was added to CISA’s KEV list and Check Point has published details on at least one attack campaign dubbed “TrueChaos” targeting the government agencies of an unnamed Southeast Asian country. The malicious update still upgraded the victim’s client from 8.5.1 to 8.5.2 to reduce suspicion.

Greenbone’s OPENVAS ENTERPRISE FEED includes an authenticated registry check to identify vulnerable installations of TrueConf Client. All versions prior to 8.5.3.884 are affected and users should upgrade TrueConf Client to version 8.5.3.884 or later.

Summary

AI-assisted vulnerability discovery has accelerated the sheer number of CVEs published each month. The increase reflects a combination of both AI-slop and legitimate critical-severity flaws in widely popular enterprise software. Anthropic’s Mythos could result in more high-impact disclosures, but so far evidence has been elusive. The SANS institute and CSA have advised organizations to essentially double their efforts towards core cyber security controls.

Defenders should employ continuous vulnerability management programs to reduce risk exposure with OPENVAS SCAN and the OPENVAS ENTERPRISE FEED for industry-leading vulnerability coverage. Greenbone produces thousands of new vulnerability tests per month to detect flaws in enterprise software applications, IT networking products, major OSs and browsers, Linux packages, productivity tools, agentic AI tooling, and more. Defenders seeking to detect and protect can try Greenbone’s entry-level OPENVAS BASIC for free, including a two-week trial of the ENTERPRISE FEED.

Published on April 29th, 2026, CVE-2026-41940 (CVSS 9.8, EPSS ≥ 95th pctl) allows unauthenticated remote attackers to gain administrative access to cPanel & WHM, and WP Squared through a missing authentication flaw [CWE-306]. Successful exploitation can grant control over hosted websites, databases, email accounts, the server operating system and configuration, and adjacent websites in shared-hosting environments.

CVE-2026-41940 has been added to CISA’s KEV list and is widely reported as actively exploited in the wild. Reports suggest the flaw was exploited as a zero-day as early as February 23, 2026. A full technical analysis and proof-of-concept (PoC) exploit code have been published by watchTowr Labs, and multiple national CERT agencies have issued alerts globally [1][2][3][4][5][6][7][8].

CVE-2025-20393-cisco-spam-filter

The potential global impact of CVE-2026-41940 is significant. cPanel’s vendor claims to have 1.5 million internet-exposed instances, roughly 70 million domains. Greenbone’s OPENVAS ENTERPRISE FEED includes a remote vulnerability check that directly verifies the exploitability of CVE-2026-41940 in cPanel and WHM instances.

Technical Details of CVE-2026-41940

CVE-2026-41940 is an authentication bypass vulnerability [CWE-306] enabled by CRLF injection during cPanel’s session loading and saving process. Session state corruption is possible due to a combination of flaws in cPanel & WHM’s session handling logic. To be clear, CVE-2026-41940 is not a single missing authentication check. It results from multiple structural software flaws that can be chained into relatively low-complexity attacks. Multi-factor authentication (MFA) offers no protection against attacks exploiting CVE-2026-41940.

Below is a description of the fundamental flaws that make up CVE-2026-41940:

  1. Inconsistent sanitization of session data is caused by a flaw in the callers tasked with remembering to sanitize data before saving it. The filter_sessiondata routine, intended to remove dangerous control characters, was not enforced inside the saveSession function itself. This allows the password value to be taken from a decoded Authorization: Basic header and written without proper sanitization to the raw session file.
  2. The second flaw involves conditional encoding of the pass (password) field. cPanel session cookies contain a session identifier and an <ob> secret segment included after a comma. However, if an attacker supplies a valid session identifier and the <ob> segment without the comma, the server still resolves the correct session file but bypasses encryption. This means the malicious password value remains in plaintext form, may include embedded carriage return or line feed (CRLF) characters, and is written directly to the session file.
  3. The third flaw is a mismatch between the raw session file format and the JSON session cache. cPanel maintains both a key=value session file and an identical JSON-serialized cache. Normal session handling loads the JSON cache, while the injected CRLF payload remains inside the pass string. However, another reachable path, Cpanel::Session::Modify, explicitly loads the raw session file containing the attacker-injected lines and copies them to the JSON cache, promoting them to top-level session attributes.
  4. The attacker can inject session attributes to bypass authentication. By providing values such as hasroot=1, tfa_verified=1, user=root, and successful_internal_auth_with_timestamp, an attacker can force a root-level authenticated session. In the WHM authentication path, an internal or external authentication timestamp bypasses verification against /etc/shadow and returns AUTH_OK.

The cPanel & WHM administrative web interface provides shellcode execution directly through the built-in terminal interfaces: WHM’s Terminal gives authorized users in-browser command line access. cPanel’s SSH Access interface also allows management of the server’s SSH service and authorized_keys, meaning a privileged attacker can hijack SSH for remote access [T1563.001].

Global Risk Assessment of CVE-2026-41940

CVE-2026-41940 presents a severe global risk because it affects widely used internet-facing hosting infrastructure, and allows unauthenticated, remote, root-level access. cPanel’s vendor claims to have 1.5 million internet-exposed instances, roughly 70 million domains. CVE-2026-41940 has been added to CISA’s KEV list, and reports suggest the flaw was exploited as a zero-day as early as February 23, 2026. watchTowr Labs has published a full technical description and detailed instructions for exploitation, further increasing the probability of widespread compromise.

CVE-2026-41940 enables a wide array of secondary attacks including:

The impact is highest for hosting providers, managed service providers, web agencies, resellers, and organizations operating shared or multi-tenant hosting environments. A single compromised WHM administrative session may give an attacker access to multiple customers’ data and email accounts. Organizations should treat any exposed, unpatched instance as potentially compromised.

Remediation Guidance for CVE-2026-41940

Organizations should treat CVE-2026-41940 as an emergency patching priority and urgently apply patches for any affected cPanel & WHM, and WP Squared instances to a fixed release. All versions of cPanel and WHM after 11.40 are affected. Mitigation requires a restart of the cPanel cpsrvd service. If immediate patching is not possible, restrict access to cPanel and WHM interfaces using firewall rules or IP allowlists, especially on ports 2083, 2087, 2095, and 2096. cPanel lists the fixed cPanel & WHM versions as:

  • 86.0.41
  • 110.0.97
  • 118.0.63
  • 124.0.35
  • 126.0.54
  • 130.0.19
  • 132.0.29
  • 134.0.20
  • 136.0.5

WP Squared has been fixed in version 136.1.7. Because CVE-2026-41940 is actively exploited, organizations should assume internet-facing instances may have been targeted before patching, and conduct a complete forensic analysis to determine system integrity. This includes reviewing authentication logs, session activity, and administrative changes for signs of unauthorized access. However, defenders should also consider that attackers may gain root-level access and subsequently affect the integrity of the server OS and system logs.

Summary

CVE-2026-41940 is a critical authentication bypass in cPanel & WHM, and WP Squared that enables unauthenticated administrative access and potential full server takeover. Active exploitation, public exploit details and widespread exposure make this an emergency for hosting providers globally. Organizations should patch immediately, restart services, and investigate exposed systems for compromise. Greenbone’s OPENVAS ENTERPRISE FEED includes a remote vulnerability check that directly verifies the exploitability of CVE-2026-41940 in cPanel and WHM instances.

Until recently, a digital product could be placed on the European market with essentially no binding cyber security standard attached to it. Manufacturers decided how much security to build in, and buyers had no assurances and no way to compare. When vulnerabilities emerged, there was no legal obligation to report or fix them. Products could be abandoned without prior notice, leaving them vulnerable to cyber attack.

The EU Cyber Resilience Act is the first EU regulation to require cyber security as a baseline condition for bringing digital products to market. Adopted in October 2024, its key obligations enter the enforcement phase in September 2026. [1] If you manufacture or distribute a digital enforcement phase in September 2026. [1] If you manufacture or distribute a digital product that is sold on the EU market, this regulation applies to you.

 

 

What Does ‘Cyber Resilience’ Actually Mean?

Cyber resilience refers to the ability to anticipate, withstand, recover from, and adapt to adverse cyber security events. The CRA operationalises cyber resilience at the market level by turning broad cyber security expectations into legally enforceable product obligations. Products must be designed to be resilient against attacks, and manufacturers must actively manage vulnerabilities throughout their product’s life cycle.

What Is a “Product With Digital Elements”?

The CRA uses the term ‘product with digital elements’ to define its scope. A product with digital elements is defined as any software or hardware product – and its remote data processing solutions – that can connect, directly or indirectly, to another device or network [2]. All things considered, this includes virtually all software that runs on a standard desktop computer, laptop, or mobile phone, and even simple hardware devices like a TV remote control.

The major product groups include:

  • Enterprise software platforms: ERP systems, CRM software, security tools, and collaboration platforms
  • Consumer hardware: smart home devices, connected appliances, routers, and IP cameras
  • Industrial products: PLCs, SCADA systems, industrial sensors, and connected machinery
  • Developer tools: IDEs, CI/CD platforms, and build tools with network connectivity
  • Operating systems: desktop, server, and embedded OS products
  • Mobile applications and other software components

 

Who Has to Comply?

The CRA places the primary obligation on manufacturers: the legal entities designing, developing, or producing products with digital elements and placing them on the EU market under their own name or trademark. But it does not end there. Importers and distributors also carry obligations. If you bring a third-party product to the EU market or make it available within the EU, you are responsible for verifying that it meets CRA requirements.

The CRA applies wherever you are based. A US software vendor selling to EU customers falls within its scope. Where a non-EU manufacturer’s products are sold in the EU by a European distributor, both parties carry obligations – the manufacturer as the entity responsible for the product, and the distributor as the entity making it available on the EU market.

The maximum fine for CRA non-compliance is €15 million or 2.5% of global annual turnover, whichever is higher – figures that concentrate board attention quickly.

What Is Explicitly Out of Scope?

  • Products covered by equivalent sector-specific legislation, such as certain medical devices, aviation equipment, and motor vehicles, where existing rules provide comparable cyber security requirements
  • Purely non-commercial open-source software (CRA still applies to open-source components of commercial products and open-source stewards)
  • National security, intelligence, and military products
  • Products not available on the market and designed exclusively for certain purposes, such as evaluation prototypes

What Does the CRA Actually Require?

At its core, the CRA requires manufacturers to do four things:

  1. Build secure digital products: Design, develop, and produce products with cyber security in mind from the start – not bolted on afterward. Products must ship without known exploitable vulnerabilities, with a minimal attack surface, and in a secure default configuration.
  2. Actively support product security: Provide security updates free of charge for at least five years. Responsibly document and manage security flaws. Maintain a Software Bill of Materials (SBOM) identifying all software components.
  3. Report exploited vulnerabilities: From 11 September 2026, report actively exploited vulnerabilities to ENISA within 24 hours and submit full technical details within 72 hours. [3]
  4. Assess and demonstrate conformity: Conduct a cyber security risk assessment before market placement. Maintain technical documentation for 10 years. Affix CE marking to demonstrate conformity. [4]

The September 2026 Deadline: Why It Matters Now

Most manufacturers are focused on the December 2027 full enforcement date – but the more immediately urgent deadline is September 11th, 2026, which kicks off vulnerability reporting obligations. That is less than five months away. From that date, any actively exploited vulnerability in your products must trigger a formal notification process to European cyber security authorities within 24 hours. [5]

Building and testing the internal process for that requires preparation. Not just a policy document, but an actual operational workflow, with tooling, escalation paths, and staff training. For security and engineering leads, September 2026 is the deadline that justifies budget conversations now — not after the 2027 full-enforcement date, when the window for orderly implementation will have closed.

What CRA Compliance Actually Requires in Practice

Meeting these obligations requires a technical foundation: you need to know what components are in your products, track which CVEs affect them, and have a way to prioritise what gets fixed first. In practice, this means vulnerability management tooling integrated into your pipeline — not as a compliance checkbox, but as a continuous process that produces a CRA-compliant audit trail. The CRA does not prescribe a specific tool, but it does prescribe the outcome: documented, traceable, repeatable vulnerability handling.

Done well, these processes can also make developers’ day-to-day work less chaotic: fewer emergency patch cycles, actionable alerts instead of raw CVE firehose output, and clear triage priority so the team is fixing what actually matters rather than everything at once.

If you are mapping out what that process needs to look like for your organisation, our upcoming posts will cover the core components of a CRA-ready vulnerability management workflow – including what an SBOM needs to contain, how exploitability scoring works in practice, and where open source tooling fits in.

On April 14th and 15th, Fortinet disclosed 27 new vulnerabilities affecting a wide range of its products. The most severe of the new flaws, CVE-2026-39808 (CVSS 9.8) and CVE-2026-39813 (CVSS 9.8) allow unauthenticated remote code execution (RCE) on the FortiSandbox service. FortiSandbox is Fortinet’s remote sandboxing and malware analysis service, distributed as on premises hardware appliances, virtual machines (VMs), and hosted cloud services. Together, these two critical CVEs generated several national CERT advisories globally [1][2][3][4][5][6][7][8][9]. A public proof of concept (PoC) for CVE-2026-39808 is publicly available, increasing the risk.

One medium severity CVE from the group, CVE-2025-61624 (CVSS 6.0), was reported by Fortinet as actively exploited, but has not been tracked in CISA’s Known Exploited Vulnerabilities (KEV) list. No details of the attack campaigns or public PoC are available.

Other Fortinet products affected by the recent disclosure include: FortiOS, FortiWeb, FortiClient EMS, FortiDDoS-F, FortiSOAR, FortiManager, FortiSwitch Manager, FortiProxy, FortiPAM, FortiAnalyzer, FortiNDR, and FortiNAC-F. Earlier in April 2026, two other CVEs, CVE-2026-35616 and CVE-2026-21643, affecting FortiClient EMS were disclosed and quickly tagged as actively exploited.

Critical vulnerabilities in FortiSandbox

Greenbone’s OPENVAS ENTERPRISE FEED includes detection coverage for all new Fortinet vulnerabilities described in this report and more. Our ENTERPRISE FEED also provides a dedicated family of tests for Fortinet vulnerabilities, helping defenders to mitigate actively evolving threats.

Start Your Free Trial

With continuously updated vulnerability detection, risk prioritization intelligence, and scalable operations, OPENVAS SCAN helps organizations strengthen their cybersecurity posture by reducing exposure to known threats across IT environments.

Start evaluating Greenbone’s flagship product, OPENVAS SCAN. Our entry level enterprise appliance, OPENVAS BASIC, is available for free and includes a two week trial of the OPENVAS ENTERPRISE FEED.

 

Risk Assessment of New Fortinet CVEs

On April 14th and 15th, Fortinet disclosed 27 new vulnerabilities, including two critical flaws, affecting FortiSandbox. Across the set of new CVEs, FortiOS, FortiWeb, FortiClient EMS, FortiDDoS-F, FortiSOAR, FortiManager, FortiSwitch Manager, FortiProxy, FortiPAM, FortiAnalyzer, FortiNDR, and FortiNAC-F are affected.

The two critical FortiSandbox flaws, CVE-2026-39808 (CVSS 9.8) and CVE-2026-39813 (CVSS 9.8), can be exploited without authentication for RCE. Together, these two critical CVEs generated several national CERT advisories globally [1][2][3][4][5][6][7][8][9] and a public proof of concept (PoC) for CVE-2026-39808 is publicly available increasing the risk.

Fortinet also reported the active exploitation of CVE-2025-61624 (CVSS 6.0). Since CVE-2025-61624 requires high level local privileges to exploit, its active exploitation indicates that attackers have either gained access to stolen credentials, have exploited other software flaws to gain high level access, or are insiders within the targeted organization.

The most important CVEs from the recently published group are:

  • CVE-2026-39808 (CVSS 9.8) affecting FortiSandbox 4.4.x: Improper neutralization of special elements [CWE-78] allows an unauthenticated attacker to execute unauthorized code or commands via specially crafted HTTP requests. Only FortiSandbox 4.4.0 through 4.4.8 are affected and users should upgrade to 4.4.9 or above. A public proof of concept (PoC) exploit is available, increasing the risk. The OPENVAS ENTERPRISE FEED includes a remote banner version check for CVE-2026-39808 [1].
  • CVE-2026-39813 (CVSS 9.8) affecting FortiSandbox 5.0.x and 4.x: A path traversal flaw [CWE-24] allows an unauthorized attacker to escalate privileges via specially crafted HTTP requests. FortiSandbox 5.0.0 through 5.0.5 and 4.4.0 through 4.4.8 are affected. The OPENVAS ENTERPRISE FEED includes a remote banner version check for CVE-2026-39813 [1].
  • CVE-2025-61624 (CVSS 6.0) affecting FortiOS, FortiPAM, FortiProxy, and FortiSwitch Manager: A path traversal flaw [CWE-22] in the command line interpreter of affected devices allows a privileged attacker to write or delete arbitrary files via specially crafted arguments to existing commands. Since CVE-2025-61624 requires high level local privileges to exploit, its active exploitation indicates that attackers have either gained access to stolen credentials, have exploited other software flaws to gain high level access, or are insiders within the targeted organization. Fortinet’s FortiOS, FortiPAM, FortiProxy, and FortiSwitch Manager are affected. The OPENVAS ENTERPRISE FEED includes a local version check for FortiOS [1] and a remote banner check for FortiProxy [2] vulnerability to CVE-2025-61624.
  • CVE-2026-39815 (CVSS 8.8) affecting FortiDDoS-F 7.2.1 through 7.2.2: An SQL injection flaw [CWE-89] allows an authenticated remote attacker to run arbitrary SQL queries on the database via specially crafted HTTP requests. Only FortiDDoS-F 7.2.1 through 7.2.2 are affected. Users should upgrade to 7.2.3 or above. The OPENVAS ENTERPRISE FEED includes a remote banner version check for CVE-2026-39815 [1].
  • CVE-2026-40688 (CVSS 7.2) affecting FortiWeb 8.0, 7.6, and 7.4: An out of bounds write vulnerability [CWE-787] vulnerability allows an authenticated remote attacker to execute arbitrary code or command via crafted HTTP requests. Fortinet FortiWeb 8.0.0 through 8.0.3, FortiWeb 7.6.0 through 7.6.6, FortiWeb 7.4.0 through 7.4.11 are affected. The OPENVAS ENTERPRISE FEED includes a remote banner version check for CVE-2026-40688 [1].
  • CVE-2026-39809 (CVSS 6.7) affecting FortiClient EMS 7.4, 7.2, and 7.0: An SQL injection flaw [CWE-89] allows authenticated remote attackers to execute unauthorized code or commands via specially crafted HTTP requests. Fortinet FortiClient EMS 7.4.0 through 7.4.5, FortiClient EMS 7.2.0 through 7.2.12, and all FortiClient EMS 7.0 versions are affected. The OPENVAS ENTERPRISE FEED includes a remote banner version check for CVE-2026-39809 [1].

Fortinet provides a mapping tool for users to determine the recommended upgrade path for their product. A complete list of CVEs for Fortinet products can be found on the vendor’s PSIRT advisories page.

Summary

Fortinet’s April 2026 disclosure introduces broad exposure across multiple product lines, with the most urgent risks centered on two critical FortiSandbox flaws that can enable unauthenticated RCE. Another vulnerability in FortiPAM, FortiProxy and FortiSwitch Manager was reported as actively exploited. Greenbone’s OPENVAS ENTERPRISE FEED covers all newly disclosed Fortinet vulnerabilities mentioned in this report and more, helping defenders identify affected systems and address remediation.

In early April, Cisco announced two critical-severity CVEs along with additional high and medium-severity vulnerabilities. Collectively, the flaws allow authentication bypass, privilege escalation to an Administrator account, unauthenticated remote code execution (RCE) as the root user, information disclosure, and Denial of Service conditions. The two critical flaws are CVE-2026-20160 (CVSS 9.8) affecting Cisco Smart Software Manager On-Prem (SSM On-Prem) and CVE-2026-20093 (CVSS 9.8) affecting Cisco Integrated Management Controller (IMC).

Greenbone’s OPENVAS ENTERPRISE FEED has included vulnerability detection for CVE-2026-20160 and CVE-2026-20093 since their disclosure, helping defenders mitigate these evolving threats. Defenders seeking to detect and protect can try Greenbone’s entry-level OPENVAS BASIC for free, including a two-week trial of the ENTERPRISE FEED.

CVE-2026-35616 and CVE-2026-21643: Fortinet EMS Actively Exploited

CVE-2026-20160 and CVE-2026-20093 pose significant threats to enterprise IT. While SSM On-Prem and IMC are both internal network services that are not meant to be publicly exposed, these CVEs may offer adversaries with a covert foothold the opportunity for lateral movement to high-value assets.

Cisco IMC is especially high risk because it is embedded in physical server and edge platforms that often sit close to core enterprise workloads. If an attacker gains administrative access, they may be able to disrupt services, pivot into adjacent networks, or use the compromised device as a staging point to target sensitive internal systems. If a target network is not strictly segmented between departments or if access controls are not tightly limited according to the principle of least privilege, risk is further increased.

Let’s first examine the two new critical-severity CVEs and then some additional CVEs published in early April 2026.

CVE-2026-20160 (CVSS 9.8) Affecting Cisco Smart Software Manager On-Prem (SSM On-Prem)

An exposed internal service allows unauthenticated remote attackers to execute arbitrary commands on the underlying OS with root privileges. CVE-2026-20160 can be exploited via HTTP requests to the exposed service’s API. The flaw is essentially an improper access control that Cisco has classified as “Exposure of Resource to Wrong Sphere” [CWE-668]. Cisco Smart Software Manager On-Prem (SSM On-Prem) versions 9-202502 to 9-202510 are affected.

Cisco SSM On-Prem is an on-premises software license-management server deployed as a virtual machine. SSM On-Prem exposes a web UI on port 8443 for administration and licensing workflows. SSM On-Prem acts as a local Smart Licensing manager for Cisco products, instead of requiring them to connect directly to Cisco’s cloud-hosted Smart Software Manager.

Multiple national CERT advisories have been issued for CVE-2026-20160 [1][2][3][4][5][6][7][8]. However, active exploitation, full technical details, or a public proof of concept (PoC) exploit are not confirmed. The OPENVAS ENTERPRISE FEED includes a remote banner version check to identify affected instances [9]. Users should update to version 9-202601 or later. See Cisco’s official advisory for more information.

CVE-2026-20093 (CVSS 9.8) Affecting Cisco Integrated Management Controller (IMC)

Improper input validation [CWE-20] can lead to authentication bypass during password change requests to the IMC. An attacker could exploit this vulnerability remotely via HTTP requests to alter the passwords of any user on the system (including an Admin user) and gain access to the system as that user.

Cisco IMC is an embedded Baseboard Management Controller (BMC) built into Cisco UCS rack and storage server platforms. The core function of Cisco IMC is out-of-band server management of physical servers when they operate in Standalone Mode via the Redfish RESTful API standard, SNMP, IPMI v2.0, or the Cisco IMC XML API. Multiple Cisco physical server products are affected if they include the Cisco Integrated Management Controller (IMC):

  • 5000 Series Enterprise Network Compute Systems (ENCS)
  • Catalyst 8300 Series Edge uCPE
  • UCS C-Series M5 and M6 Rack Servers in standalone mode
  • UCS E-Series Servers M3
  • UCS E-Series Servers M6

Multiple national CERT advisories have been issued for CVE-2026-20093 [1][2][3][4][5][6][7]. However, active exploitation, full technical details, or a public proof of concept (PoC) exploit are not confirmed. Greenbone’s OPENVAS ENTERPRISE FEED includes an active check [9] and a remote banner version check [10] for devices affected by CVE-2026-20093. See Cisco’s official advisory for more information including a list of fixed releases for affected products.

Other Recent High-Severity Flaws in Cisco Products

Cisco also disclosed several high and medium-severity vulnerabilities that expand the risk posed to enterprise customers. While all of the CVEs below require valid account access to exploit, credential theft is a common tactic used in many sophisticated cyber attacks. If unpatched, these flaws could still result in command execution, privilege escalation, denial of service, or sensitive information exposure.

  • CVE-2026-20094 (CVSS 8.8): A command injection flaw due to improper validation of user-supplied input [CWE-77] allows an authenticated, remote attacker with read-only privileges to execute arbitrary commands on the underlying OS with root privileges. The flaw is exploitable via HTTP requests. The web-based management interface of Cisco IMC and Cisco Enterprise NFVIS version 4.18.x and prior are affected. A full list of affected products and fixed releases are available in Cisco’s official advisory.
  • CVE-2026-20155 (CVSS 8.0): Improper authorization checks [CWE-862] on an API endpoint allow an authenticated, remote attacker with low privileges to access sensitive information without authorization. The flaw affects the web-based management interface of Cisco Evolved Programmable Network Manager (EPNM) devices prior to version 8.1.2 for all configurations. More information is available in Cisco’s official advisory.
  • CVE-2026-20151 (CVSS 7.3): Due to the improper transmission of sensitive user information [CWE-201], an attacker can retrieve session credentials from status messages to elevate privileges from a low-level account to admin. SSM On-Prem version 9-202510 and earlier in all configurations are affected. More information is available in Cisco’s official advisory.
  • CVE-2026-20095 (CVSS 6.5): Due to improper validation of user-supplied input, an authenticated remote user can execute arbitrary code or commands [CWE-77] on the underlying OS of an affected system and elevate privileges. The flaw is exploitable via HTTP requests. The web-based management interface of Cisco IMC and Cisco Enterprise NFVIS version 4.18.x and earlier are affected. A full list of affected products and fixed releases are available in Cisco’s official advisory.
  • CVE-2026-20096 (CVSS 6.5): Due to improper validation of user-supplied input, an authenticated remote admin user can execute arbitrary commands [CWE-77] on the underlying OS with root privileges. The flaw is exploitable via HTTP requests. The web-based management interface of Cisco IMC and Cisco Enterprise NFVIS version 4.18.x and prior are affected. A full list of affected products and fixed releases are available in Cisco’s official advisory.
  • CVE-2026-20097 (CVSS 6.5): Due to improper validation of user-supplied input, an authenticated remote admin user can execute arbitrary commands [CWE-77] on the underlying OS with root privileges. The web-based management interface of Cisco IMC and Cisco Enterprise NFVIS version 4.18.x and prior are affected. A full list of affected products and fixed releases are available in Cisco’s official advisory.
  • CVE-2026-20110 (CVSS 6.5): A vulnerability in the CLI of Cisco IOS XE Software could allow an authenticated, local attacker to cause a denial of service (DoS) condition. This vulnerability exists because incorrect privileges are associated with the start maintenance All versions of Cisco IOS XE Software are affected if the start maintenance command is supported. See Cisco’s official advisory for more information.

Cisco has assigned a Security Impact Rating (SIR) of High to CVE-2026-20095, CVE-2026-20096, and CVE-2026-20097, which is above their CVSS ranking of Medium, because additional security implications apply if an attacker gains root-level access. The OPENVAS ENTERPRISE FEED includes detection tests for all aforementioned CVEs [1][2][3][4][5].

Summary

Cisco’s early April 2026 security disclosures indicate elevated risk across several products. This includes the vendor’s SSM On-Prem license management server and Cisco Integrated Management Controller (IMC), which impacts a wide array of physical hardware products, including Cisco UCS rack and storage server platforms. The most severe new flaws enable authentication bypass and unauthenticated RCE as the root user.

Although public exploitation has not been confirmed, the affected systems are high-value internal assets that represent attractive targets for advanced persistent threat (APT) actors. Organizations should verify exposure to these and other software vulnerabilities and prioritize patching. Defenders seeking to detect and protect can try Greenbone’s entry-level OPENVAS BASIC for free, including a two-week trial of the ENTERPRISE FEED.

Fortinet FortiClient EMS faces immediate risk from two critical severity CVEs: CVE-2026-35616 in versions 7.4.5-7.4.6 and CVE-2026-21643 in 7.4.4. CVE-2026-35616 (CVSS 9.8) is an actively exploited vulnerability in Fortinet FortiClient Enterprise Management Server (EMS) 7.4.5 through 7.4.6, published on April 4, 2026. The flaw is an improper access control [CWE-284] that can be exploited for unauthenticated remote code execution (RCE). An attacker exploiting CVE-2026-35616 may execute unauthorized code or commands through maliciously crafted HTTP requests. Because it was disclosed over the holidays, only a few national CERT alerts have so far been issued for CVE-2026-35616 [1][2]. CVE-2026-21643 is the second actively exploited flaw identified in Fortinet FortiClient EMS in recent weeks. Defused Cyber recently detected campaigns attacking CVE-2026-21643 (CVSS 9.8), also affecting Fortinet FortiClient EMS.

Greenbone’s OPENVAS ENTERPRISE FEED includes separate remote banner checks for CVE-2026-35616 [3] and CVE-2026-21643 [4] and provides a dedicated family of tests for Fortinet vulnerabilities, allowing defenders to mitigate actively evolving threats.

CVE-2026-35616 and CVE-2026-21643: Fortinet EMS Actively Exploited

FortiClient EMS is Fortinet’s central management server for deploying, configuring, updating, and monitoring FortiClient enabled endpoints across enterprise environments. In security operations, FortiClient EMS helps enforce endpoint security policies, maintain visibility into device posture and compliance, and coordinate endpoint controls with the broader Fortinet ecosystem.

Start Your Free Trial

With continuously updated vulnerability detection, risk-prioritization intelligence, and scalable operations, OPENVAS SCAN helps organizations strengthen their cybersecurity posture by reducing exposure to known threats across IT environments.

Start evaluating Greenbone’s flagship product, OPENVAS SCAN. Our entry-level enterprise appliance, OPENVAS BASIC, is available for free and includes a two-week trial of the OPENVAS ENTERPRISE FEED.

 

Risk Assessment for CVE-2026-35616

Active exploitation of CVE-2026-21643 (CVSS 9.8) was acknowledged in Fortinet’s security advisory (FG-IR-26-099) on April 4th. Defused Cyber is credited with detection of zero-day active attacks and responsible disclosure to the vendor. Watchtowr Labs has also reported detecting attacks since March 31, 2026. CVE-2026-35616 was added to CISA’s KEV catalog on April 6th and an aggressive patch deadline of April 9th was set for U.S. federal agencies.

No specific technical analysis, proof-of-concept (PoC) exploit, or attack campaign details are publicly available for CVE-2026-35616. The risk is elevated because the CVE was exploited as a zero-day, showing that adversaries have already developed exploit tooling. The Shadowserver dashboard indicates ~2,000 exposed FortiClient EMS instances remain reachable on the internet; however, this may include honeypot devices.

Risk Assessment for CVE-2026-21643

CVE-2026-21643 (CVSS 9.8) introduced during Fortinet’s refactor of the database connection layer in version 7.4.4, and quickly patched in version 7.4.5. In recent weeks, Defused Cyber reported campaigns attacking CVE-2026-21643, which also affects Fortinet FortiClient EMS. Covered briefly in our March 2026 Threat Report, CVE-2026-21643 is an SQL injection flaw [CWE-89] potentially leading to unauthenticated RCE via specifically crafted HTTP requests. Numerous national CERT alerts have been issued [5][6][7][8][9][10][11][12][13][14][15][16][17]. CVE-2026-21643 has not yet been added to CISA’s KEV list.

A technical root-cause analysis for CVE-2026-21643 has been published enabling rapid exploit development.  According to the analysis, exploitability depends on the multitenancy feature being enabled via the SITES_ENABLED=True configuration. If multitenancy is disabled, the middleware vdom is hardcoded and does not read the attacker-controlled Site header. The vulnerable path remains present but effectively unreachable.

Mitigating CVE-2026-35616 and CVE-2026-21643 in Fortinet FortiClient EMS

Fortinet’s advisory states that only FortiClient EMS 7.4.5 through 7.4.6 are affected; FortiClient EMS 7.2 is not affected. The immediate mitigation for CVE-2026-35616 is to apply the appropriate emergency hotfix listed in Fortinet’s official advisory for FortiClient EMS 7.4.5 or 7.4.6. Applying the hotfix does not require system downtime.

While CVE-2026-35616 affects versions 7.4.5 through 7.4.6, CVE-2026-21643 affects the earlier 7.4.4 and is mitigated by upgrading to 7.4.5 or later. Instances on earlier versions should first upgrade to at least 7.4.5 and then apply the appropriate hotfix.

According to Fortinet, FortiClientEMS version 7.4.7 will also include the fix for this issue when it is released. Greenbone’s OPENVAS ENTERPRISE FEED includes separate remote banner checks for CVE-2026-35616 [3] and CVE-2026-21643 [4] and provides a dedicated family of tests for Fortinet vulnerabilities, allowing defenders to detect and mitigate actively evolving threats.

Summary

Fortinet FortiClient EMS faces immediate risk from two critical, actively exploited vulnerabilities: CVE-2026-35616 in versions 7.4.5-7.4.6 and CVE-2026-21643 in version 7.4.4. Organizations should urgently identify exposed EMS servers, upgrade affected installations, and apply Fortinet’s emergency hotfixes without delay. Greenbone’s OPENVAS ENTERPRISE FEED can help defenders detect vulnerable systems and prioritize remediation.

This month exposed new cyber security risks at all levels of enterprise IT infrastructure. New critical vulnerability exposure emerged in perimeter networking gear and core network appliances. Other risks included actively exploited flaws in major browsers, enterprise email clients, agentic workflow platforms, core OS components, and virtually every other aspect of the enterprise IT ecosystem. In 2026, hunting for new vulnerabilities regularly is a fundamental cyber security activity and an essential component of an Exposure Management approach to cybersecurity.

CVE-2025-20393-cisco-spam-filter

Defenders seeking to detect and protect can try Greenbone’s OPENVAS BASIC for free, including a two-week trial of the OPENVAS ENTERPRISE FEED.

CitrixBleed 3: Memory Leak in Citrix Netscaler ADC and Gateway Actively Exploited

CVE-2026-3055 (CVSS 9.3) is a memory disclosure flaw that is exploitable remotely and without authentication. The root cause is insufficient input validation allowing out-of-bounds memory read access [CWE-125]. The flaw affects NetScaler ADC and NetScaler Gateway appliances configured as a SAML Identity Provider (IDP), reported to be a common single-sign-on (SSO) configuration.

Active reconnaissance for authentication methods in the /cgi/GetAuthMethods endpoint was reported 3 days post-disclosure. On March 30th, CVE-2026-3055 was added to CISA’s KEV list and was reported as actively exploited by other sources. A full technical analysis with exploit code has been published. The flaw resembles previous memory leak flaws affecting Netscaler ADC and Gateway, dubbed CitrixBleed and CitrixBleed 2, whose use for initial access is well documented [1][2][3][4]. Several national cyber security agencies have issued alerts for the new CVEs [5][6][7][8][9][10][11][12][13][14][15][16][17][18].

Citrix reported another high severity flaw in the same report. CVE-2026-4368 (CVSS 7.7) is a race condition bug that can cause user session mix-up on gateway or AAA virtual server configurations. See the official security advisory for more information, including affected versions for both new CVEs. Greenbone’s OPENVAS ENTERPRISE FEED includes a remote banner check to identify appliances that are potentially vulnerable to CVE-2026-3055 [19] and a similar check for CVE-2026-4368 [20].

SharePoint Actively Exploited, RegPwn, and Other Emerging Microsoft Risks

CVE-2026-20963 (CVSS 8.8, EPSS ≥ 91st pctl) affecting Microsoft SharePoint and published in January 2026, was added to CISA’s KEV list in March. The flaw is caused by improper deserialization of untrusted data [CWE-502] and could allow arbitrary remote code execution (RCE) to an authenticated attacker. The vulnerability attracted global attention from national CERT agencies [1][2][3][4][5][6][7][8][9][10][11]. Greenbone’s OPENVAS ENTERPRISE FEED includes detection for Microsoft SharePoint Server 2019 and Microsoft SharePoint Enterprise Server 2016 [12][13].

Other high-profile risks affecting Microsoft products in March 2026 include:

  • CVE-2026-24291 (CVSS 7.8): An incorrect permission assignment for a critical resource [CWE-732] in Windows Accessibility Infrastructure (ATBroker.exe) allows an authorized local attacker to elevate privileges and modify Windows Registry keys. Dubbed RegPwn, full technical descriptions [14][15] and proof-of-concept (PoC) exploit code are publicly available, increasing risk. The OPENVAS ENTERPRISE FEED includes registry checks for vulnerability detection across Windows OS versions.
  • CVE-2026-26110 (CVSS 7.8): A type confusion flaw [CWE-843] in Microsoft Office allows an unauthorized local attacker to execute arbitrary code with high-level privileges. The OPENVAS ENTERPRISE FEED includes package version detection for Windows and macOS versions of Microsoft Office [16][17].
  • CVE-2026-26113 (CVSS 7.8): An untrusted pointer dereference vulnerability [CWE-822] in Microsoft Office allows an unauthorized local attacker to execute arbitrary code with high-level privileges. The OPENVAS ENTERPRISE FEED includes package version detection for Windows and macOS versions of Microsoft Office [16][17] and SharePoint for Windows [18][19].

CVE-2026-33017: Langflow API Actively Exploited for Unauthenticated RCE

CVE-2026-33017 (CVSS 9.8, EPSS ≥ 90th pctl) is an unauthenticated RCE flaw that can be exploited via malicious HTTP request. The CVE affects any network-exposed Langflow instances prior to version 1.9.0. CVE-2026-33017 has been reported as actively exploited by multiple sources [1][2]. Several technical analyses [2][3][4] and public PoC exploits [3] exist, increasing the risk. Multiple CERT alerts have been issued globally [5][6][7][8][9].

Langflow is an open-source “low-code” platform for building, testing, and deploying agentic AI and LLM-enabled workflows. The flaw exists in Langflow’s API endpoint for building public flows. By design, the POST /api/v1/build_public_tmp/{flow_id}/flow endpoint allows building public flows without authentication. The official Langflow API documentation states that Build Public Tmp only works for workflows marked as public in the database. The vulnerability arises when the optional data parameter is supplied: Langflow uses attacker-controlled flow code, which may contain arbitrary Python code, instead of the stored code from the database. This code is passed to exec() without sandboxing, resulting in unauthenticated RCE.

The OPENVAS ENTERPRISE FEED includes a remote banner check to identify vulnerable instances of Langflow. Users should upgrade to version 1.9.0.

Living On The Edge: Perimeter Security Risks Emerging in March 2026

Exploitation of perimeter networking devices has been consistently measured as a top initial-access vector in cyber breaches. New vulnerabilities affecting key perimeter devices are published continuously and defenders need to be able to detect and patch these exposed entry points reliably. Here are several high-risk vulnerabilities affecting perimeter networking devices that emerged in March 2026:

New Cisco Firewall Flaws Ignite Perimeter Risk

Cisco published a group of 48 CVEs affecting its firewall product line, including two critical CVSS 10 vulnerabilities. One of these, CVE-2026-20131, was soon added to CISA’s KEV list. Active exploitation was also confirmed by Cisco. Ransomware attacks exploiting CVE-2026-20131 have been attributed to the Interlock threat actor. Numerous national CERT advisories have been issued globally [1][2][3][4][5][6][7][8][9][10][11][12][13][14].

Greenbone’s OPENVAS ENTERPRISE FEED includes detection tests for all 48 CVEs disclosed in Cisco’s security advisory, and a family of tests dedicated to Cisco software flaws. Users are advised to identify affected products in their network, apply patches immediately, and conduct breach assessments by hunting for any indicators of compromise (IoCs) [15]. The highest risk CVEs from the group are described below:

  • CVE-2026-20131 (CVSS 10, EPSS 71st pctl): Insecure deserialization [CWE-502] of a user-supplied Java byte stream allows unauthenticated Java RCE with root privileges. The flaw affects the web-based management interface of Cisco Secure Firewall Management Center (FMC). If the FMC management interface is not internet accessible, the attack surface is significantly reduced.
  • CVE-2026-20079 (CVSS 10, EPSS 90th pctl): An flawed system process is created at boot time that allows a remote attacker to bypass authentication [CWE-288] via crafted HTTP requests and execute script files. This may allow an attacker to obtain root privileges on the underlying OS. A full technical analysis and PoC exploit code are publicly available, increasing the risk. CVE-2026-20079 affects the web interface of Cisco Secure FMC.

CVE-2026-22557: CVSS 10 Unauthenticated Account Takeover on Ubiquiti UniFi Network Application

CVE-2026-22557 (CVSS 10) allows unauthorized account takeover through a path-traversal flaw [CWE-22] that lets attackers manipulate files on the underlying system. Public technical details are available and researchers assess that automated exploitation is trivial. Risk is also elevated because Ubiquiti network products are widely used. Multiple national CERT agencies have issued alerts globally [1][2][3][4][5].

Another CVE published in the same vendor advisory imposes additional high risk:

  • CVE-2026-22559 (CVSS 8.8): An input validation flaw that is exploitable via social engineering if an attacker can trick the victim with network access to a Ubiquiti UniFi Network Application web interface to click on a malicious link.

CVE-2026-22557 affects Ubiquiti UniFi Network Application version 10.1.85 and earlier, Release Candidate 10.2.93 and earlier, and UniFi Express version 9.0.114 and earlier. OPENVAS ENTERPRISE FEED includes a remote banner check to identify affected instances. Mitigation instructions for both aforementioned CVEs are available on the vendor’s official security advisory.

Other Notable Security Risks Affecting Perimeter Networking Devices

Other emerging threats to perimeter networking devices in March 2026 include:

F5 BIG-IP APM Access Policy

!
Update April 6th, 2026
On March 28th, 2026, CVE-2025-53521 CVSS 9.8 described below, was reclassified by the vendor F5 to indicate a Remote Code Execution (RCE) impact rather than only a Denial of Service (DoS) impact, significantly increasing risk to potential victims.

CVE-2025-53521 (CVSS 7.5) is an actively exploited flaw that allows attackers to trigger Denial of Service (DoS) on F5 BIG-IP if an APM Access Policy is configured on a virtual server. National CERT agencies have issued alerts [1][2][3][4][5][6][7][8][9][10][11][12][13][14]. The OPENVAS ENTERPRISE FEED provides package-level detection for CVE-2025-53521 and a dedicated family of F5 security checks.

Juniper Networks Junos OS Evolved on PTX Series

CVE-2026-21902 (CVSS 9.8) is an Incorrect Permission Assignment for Critical Resource flaw [CWE-732] that allows unauthenticated RCE as root. CVE-2026-21902 affects the On-Box Anomaly detection framework of Juniper Networks Junos OS Evolved on PTX Series. The On-Box Anomaly detection framework is enabled by default. This flaw affects all PTX Series 25.4 versions before 25.4R1-S1-EVO and 25.4R2-EVO. This issue does not affect Junos OS Evolved versions before 25.4R1-EVO or Junos OS. A detailed technical description is publicly available reducing the burden for exploit development. Numerous national CERT agencies have published alerts [1][2][3][4][5][6][7][8][9][10][11]. An active check and a remote banner check are available in the OPENVAS ENTERPRISE FEED and a dedicated family of authenticated security checks for JunOS. See the vendor’s official advisory for more information.

Critical and High-Severity Flaws in HPE Aruba Networking Products

Hewlett-Packard Enterprise (HPE) published an advisory on March 10th, disclosing one critical and three high-severity CVEs in their Aruba networking AOS-CX switches. Multiple national CERT advisories were issued globally for the group of vulnerabilities [1][2][3][4][5][6][7][8][9][10][11][12]. Greenbone’s OPENVAS ENTERPRISE FEED includes a remote banner check for all CVEs disclosed in the advisory, which are described below. Users are strongly encouraged to identify any vulnerable AOS-CX appliances in their environment and update to the most recent version.

  • CVE-2026-23813 (CVSS 9.8): An improper authentication flaw [CWE-287] in the web-based management interface of AOS-CX switches allows an unauthenticated remote attacker to circumvent existing authentication controls, including resetting the admin password.
  • CVE-2026-23814 (CVSS 8.8): A command injection flaw [CWE-77] affecting the parameters of certain AOS-CX command-line interface (CLI) commands could allow an authenticated low-privilege remote attacker to inject malicious commands.
  • CVE-2026-23815 (CVSS 7.2): A command injection flaw [CWE-77] in a custom binary used in the AOS-CX CLI could allow an authenticated remote attacker with high privileges to execute unauthorized commands.
  • CVE-2026-23816 (CVSS 7.2): A command injection flaw [CWE-77] in the command line interface of AOS-CX switches could allow an authenticated remote attacker to execute arbitrary commands on the underlying operating system.
  • CVE-2026-23817 (CVSS 6.5): A vulnerability in the web-based management interface of AOS-CX switches could allow an unauthenticated remote attacker to redirect users to an arbitrary URL [CWE-601].

A Spotlight on Shadow IT: OpenClaw (Clawd/Moltbot) AI Agent

OpenClaw (previously Clawd and Moltbot) is an open-source agentic AI assistant that can execute system-level tasks on behalf of a human user. OpenClaw’s capabilities include sending email, reading and writing files, and interacting with web services and APIs. The software was originally released as Clawd in November 2025, was rebranded to Moltbot in early 2026, and then rebranded again to OpenClaw [1].

Despite OpenClaw’s rise in popularity, criticism from the security community has been harsh [2][3][4][5]. Germany’s BSI listed over 60 vulnerabilities, and since its release, over 200 CVEs have been issued for the popular but unstable AI agent including 32 critical severity CVEs released in March 2026 alone. The most severe of the vulnerabilities allow unauthenticated RCE in the OpenClaw context. National CERT alerts have been issued for the product [1][2][3].

Considering the operational risks to unauthorized access and data security that OpenClaw poses to organizations, it should be banned from use. The OPENVAS ENTERPRISE FEED includes remote and local authenticated product detection for OpenClaw. Security teams can set alerts to notify them if OpenClaw is detected within their network.

Unauthenticated RCE in Wazuh Manager via Cluster Mode Worker Nodes

CVE-2026-25769 (CVSS 9.1) is an RCE that allows an authorized attacker with access to a cluster worker node to execute code on the master node as root. The root cause is flawed deserialization of untrusted data [CWE-502]. Risk is elevated because successful compromise of any worker in cluster mode can lead to full root-level compromise of the master node. A full technical analysis and PoC exploit kit are publicly available for CVE-2026-25769 lowering the barrier for attackers. Several national CERT agencies have issued alerts [1][2][3].

Five other CVEs were included in the disclosure by Wazuh including one additional critical severity flaw: CVE-2025-30201 (CVSS 9.1) allows authenticated attackers to force NTLM authentication through malicious UNC paths via agent configuration settings, potentially leading NTLM relay attacks [CWE-294] for privilege escalation and RCE. Technical detail and a PoC exploit are publicly available online.

The newly disclosed CVEs affect various version ranges of Wazuh Manager, but all require patching to version 4.14.3 or higher. The OPENVAS ENTERPRISE FEED includes detection for all aforementioned CVEs [1][2][3][4], and prior vulnerabilities affecting Wazuh. Users should consult Wazuh’s security advisories for specific details on each vulnerability.

n8n Agentic Workflow Platform Exposes New Critical Flaws

In recent months numerous critical and high-severity vulnerabilities have been exposed in the popular agentic workflow platform n8n. Attackers are starting to take advantage; on March 11th, 2026, CVE-2025-68613 (CVSS 8.8) was added to CISA’s KEV list. CVE-2025-68613 and other n8n flaws were covered in Part 2 of the January 2026 Threat Report.

Flawed expression evaluation has been a common cause of vulnerabilities. n8n expressions are specially formatted strings that allow dynamic manipulation of data for batch processing tasks, among other use cases. The highest-risk CVEs affecting n8n that emerged in March 2026 include:

  • CVE-2026-27495 (CVSS 9.9): An authenticated user with workflow permissions can exploit a vulnerability in the JavaScript Task Runner to execute arbitrary code outside the sandbox boundary. On instances using the default internal Task Runners this could result in full compromise of the n8n host. Exploitability depends on Task Runners being enabled with the N8N_RUNNERS_ENABLED=true setting.
  • CVE-2026-27577 (CVSS 9.9): An authenticated user with workflow permissions can abuse crafted expression parameters to trigger unintended command execution on the n8n host. This flaw allows bypass of security measures put in place to restrict command execution capabilities.
  • CVE-2026-33696 (CVSS 8.8): An authenticated user with workflow permissions can exploit a prototype pollution vulnerability in the XML and GSuiteAdmin nodes. By supplying crafted parameters as part of node configuration, an attacker could write attacker-controlled values onto `Object.prototype` and achieve RCE.
  • CVE-2026-33660 (CVSS 9.4): An authenticated user with workflow permissions can use the Merge node’s “Combine by SQL” mode to read local files on the n8n host and achieve RCE.

The OPENVAS ENTERPRISE FEED includes detection for all CVEs mentioned above [1][2][3][4] and other known n8n flaws. Each flaw affects various v1.x and v2.x instances of n8n. In many cases, if patches cannot be applied immediately, system administrators may disable affected nodes using the NODES_EXCLUDE environment variable. However, there are no workarounds offering full mitigation for any of the CVEs. Mitigation depends on updating to the latest version of n8n. See n8n’s security advisories for a complete list of vulnerabilities with descriptions.

Other Notable Critical Risk CVEs Emerging in March 2026

Let’s wrap up this month’s threat report with a quick-fire of other emerging threats in March 2026:

CVE-2026-3564 (CVSS 9.0) in ConnectWise ScreenConnect prior to version 26.1

An attacker with access to configuration files can extract a device’s machine key and use it for session authentication. ScreenConnect is a remote support and remote access platform that lets IT staff securely connect to attended or unattended devices. Several national CERT alerts have been issued [1][2][3]. The OPENVAS ENTERPRISE FEED includes a remote banner check to identify affected instances.

CVE-2026-27944 (CVSS 9.8) in Nginx UI prior to v2.3.3

An unauthenticated remote attacker can download a full backup of the underlying system containing sensitive data, including user credentials, session tokens, SSL private keys, and Nginx server configurations. The flaw is due to the /api/backup endpoint being accessible without authentication and disclosing the encryption keys to decrypt the backup. Full technical analysis and PoC exploits are publicly available [1][2] and several national CERT alerts have been issued [3][4][5][6][7][8]. Nginx UI is a web user interface for the Nginx web server. The OPENVAS ENTERPRISE FEED includes an active check to identify affected instances.

CVE-2025-66168 (CVSS 8.8) in Apache ActiveMQ Message Broker

An integer overflow flaw [CWE-190] results in failure to properly validate the MQTT control packet’s remaining length field. Exploitation may lead to unexpected behavior including Denial of Service (DoS). The OPENVAS ENTERPRISE FEED includes a remote banner check to identify affected Apache ActiveMQ instances. See the vendor’s announcement for more details.

CVE-2026-1603 (CVSS 7.3, EPSS 65th pctl) in Ivanti Endpoint Manager prior to 2024 SU5

A new actively exploited authentication bypass vulnerability [CWE-288] could be exploited to leak credential data from Ivanti Endpoint Manager devices before version 2024 SU5. The OPENVAS ENTERPRISE FEED includes a remote banner check to detect CVE-2026-1603 and CVE-2026-1602 (CVSS 6.5). The two CVEs were disclosed in February 2026, and patches are available from Ivanti’s security advisory. No PoC exploit or detailed technical analysis are publicly available.

CVE-2026-21643 (CVSS 9.8) in FortiClientEMS v7.4.x prior to v7.4.5

!
Update April 6th, 2026
Attacks exploiting CVE-2026-21643 CVSS 9.8 described below, were reported by Defused Cyber. However, CVE-2026-21643 has not been added to CISA’s KEV list as of April 6th, 2026.

An improper neutralization of special elements allows SQL injection [CWE-89] in Fortinet FortiClientEMS 7.4.x prior to v7.4.5. Exploitation can lead to unauthenticated RCE via specifically crafted HTTP requests. A technical root-cause analysis has been published potentially enabling rapid exploit development. Numerous national CERT alerts have been issued [1][2][3][4][5][6][7][8][9][10][11][12][13]. The OPENVAS ENTERPRISE FEED provides a remote banner check for CVE-2026-21643. Update to version 7.4.5 or later. See Fortinet’s official advisory for more information.

Summary

March 2026 brought new cyber risk at all levels of enterprise IT infrastructure. Perimeter networking gear and network appliances were hit especially hard. Other emerging threats included actively exploited flaws in major browsers, enterprise email clients, agentic workflow platforms, core OS components, and virtually every other aspect of the enterprise IT ecosystem. In 2026, hunting for new vulnerabilities regularly is a fundamental cyber security activity, and an essential component of an Exposure Management approach to cybersecurity.

Defenders seeking to detect and protect can try Greenbone’s OPENVAS BASIC for free, including a two-week trial of the OPENVAS ENTERPRISE FEED.

On March 12th, 2026, Veeam published two security advisories containing 7 critical and one high-severity vulnerability in its Backup & Replication server. The flaws cumulatively affect the version 12 and 13 builds. Although there are no reports of active exploitation or public proof-of-concept (PoC) exploits available yet, Veeam has appeared on CISA’s Known Exploited Vulnerabilities (KEV) list four times since late 2022, each instance associated with ransomware attacks [1][2][3]. Veeam and other enterprise backup systems are typically high-value targets for ransomware operators due to their role in securing critical data. Several national CERT alerts have been issued globally for the new CVEs [4][5][6][7][8][9][10].

Greenbone’s OPENVAS ENTERPRISE FEED includes remote banner checks for all CVEs referenced in the new advisories [11][12] and provides consistent detection for vulnerabilities affecting Veeam Backup & Replication [13][14][15][16]. Defenders seeking to detect and protect can try Greenbone’s flagship OPENVAS BASIC for free, including a two-week trial of the OPENVAS ENTERPRISE FEED.

7 kritische Schwachstellen in Veeam Backup & Replication

8 New CVEs Impacting Veeam Backup & Replication

All the newly disclosed vulnerabilities require user authentication to exploit. However, attackers with stolen credentials [TA0006] or malicious insiders could exploit these flaws. According to IBM’s 2025 Threat Intelligence Index, nearly half of all cyber attacks resulted in stolen data or credentials, and identity abuse was tied with exploitation of public facing applications for the most common entry point. IBM’s report also revealed an 84% increase in emails delivering infostealers in 2024.

Each new flaw affects version 12 and/or version 13 builds of Veeam Backup & Replication server. One from the group, (CVE-2026-21672) only affects Windows-based instances. The rest affect both WIndows and Linux builds. The 8 new vulnerabilities were disclosed by the vendor in two separate advisories [17][18]. However, technical details have not been published for any of the alerted CVEs.

Greenbone’s OPENVAS ENTERPRISE FEED includes remote banner checks covering all new CVEs [8][9]. Defenders seeking to detect and protect can try Greenbone’s flagship OPENVAS BASIC for free, including a two-week trial of the OPENVAS ENTERPRISE FEED.

The CVEs are described below, along with the impact and affected products:

CVE ID CVSS Impact Affected Products

CVE-2026-21708

9.9

A user with Backup Viewer permissions can perform remote code execution (RCE) as the postgres user

≤ v12.3.2.4165 of v12 builds

≤ v13.0.1.1071 of v13 builds

CVE-2026-21666

9.9

An authenticated domain user can perform RCE on the Backup Server

≤ v12.3.2.4165 of v12 builds

CVE-2026-21667

9.9

An authenticated domain user can perform RCE on the Backup Server

≤ v12.3.2.4165 of v12 builds

CVE-2026-21669

9.9

An authenticated domain user can perform RCE on the Backup Server

≤ v13.0.1.1071 of v13 builds

CVE-2026-21668

8.8

An authenticated domain user to bypass restrictions and manipulate arbitrary files on a Backup Repository

≤ v12.3.2.4165 of v12 builds

CVE-2026-21672

8.8

Allows local privilege escalation on Windows-based Veeam Backup & Replication servers.

≤ v12.3.2.4165 of v12 builds for Windows

≤ v13.0.1.1071 of v13 builds for Windows

CVE-2026-21671

9.1

An authenticated user with the Backup Administrator role can perform RCE in high availability (HA) deployments of Veeam Backup & Replication

v13.0.1.1071 and earlier v13 builds of Veeam Backup & Replication servers

CVE-2026-21670

7.7

Allows a low-privileged user to extract saved SSH credentials

v13.0.1.1071 and earlier v13 builds of Veeam Backup & Replication servers

Mitigation of New Veeam Backup & Replication CVEs

No workarounds have been published for any of the aforementioned vulnerabilities. Organizations running affected Veeam Backup & Replication servers should apply the vendor’s fixed builds as soon as possible:

  • Version 12 users should upgrade to 3.2.4465 or later
  • Version 13 users should upgrade to 0.1.2067 or later

All earlier version 12 or 13 builds should be treated as vulnerable. Defenders should also evaluate their credential security to strengthen their protection against software flaws that require authentication to exploit. Stolen credentials, overprivileged accounts, and exposed administrative access increase the risk of compromise.

Summary

Veeam has disclosed eight new vulnerabilities in its Backup & Replication product, including seven critical flaws affecting version 12 and 13 builds. Although no active exploitation has been reported, backup platforms remain frequent ransomware targets. Because no workarounds are available, affected organizations should patch immediately to version 12.3.2.4465 or 13.0.1.2067 and take steps to strengthen credential security.

Greenbone’s OPENVAS ENTERPRISE FEED includes remote banner checks for all CVEs in the new advisories [8][9] and provides consistent detection for vulnerabilities affecting Veeam Backup & Replication [13][14][15][16]. Defenders seeking to detect and protect can try Greenbone’s flagship OPENVAS BASIC for free, including a two-week trial of the OPENVAS ENTERPRISE FEED.

 

Kontakt Kostenlos testen Hier kaufen Zurück zur Übersicht

A field report on open source, competition, enforcement of rights, and the question of how to defend a fair and sustainable open source ecosystem.

Summary

This report describes a real case of misuse of open source software using the example of OPENVAS, the open source vulnerability management system we developed. A market participant had systematically integrated open-source code and data into its own products in violation of license and copyright laws and passed them off as its own work. Here, we report on the technical, forensic, and legal steps that were necessary to prove the misuse and effectively stop it, including warning letters, preliminary injunctions, and the involvement of platform operators. Special attention is paid to a case that was successfully brought in Germany for the first time to enforce the Open Database License (ODbL). The article is aimed at open-source developers, companies, and users and shows the requirements and costs associated with enforcing open source licenses—and why their consistent defense is crucial for a fair and sustainable open source ecosystem.

An in-depth analysis from a legal perspective has been published by IFROSS.

The peacocks and the crow in IT security

The Peacocks and the Crow

Fab. Aesop. 188. Phaedrus lib. I. Fab. 3.

A proud crow adorned itself with the colorful feathers of the peacocks and, when it believed itself to be sufficiently adorned, boldly mingled with these splendid birds of Juno.
It was recognized, and quickly the peacocks fell upon it with their sharp beaks to tear off its deceitful finery.
“Stop!” she finally cried, “you all have your feathers back now.” But the peacocks, some of whom had noticed the crow’s own shiny wing feathers, replied:
“Be quiet, you poor fool, these cannot be yours either!” – and continued to peck at her.

When software vendors want to adorn themselves with borrowed plumes, open source is an easy source. Of course, this is not compatible with open source licenses, but who cares? “What’s the worst that could happen?” seem to say some who even build their own business models on the work of others, which they also pass off as their own. Anyone who wants to fight back has a long road ahead of them and will have many interesting and not always pleasant experiences along the way. We did that, and here is our report.

With OPENVAS, we produce a globally popular and widely used open source vulnerability management system. Our project automates the search for security vulnerabilities in IT systems. We have around 200,000 tests to find security vulnerabilities, plus scanners to run them and applications to control the entire process from scanning to reporting. We provide an open source solution free of charge, as well as additional modules and services for our paying customers. This allows us to finance ourselves and also make the solution available to the community free of charge. What we do makes us at least competitive with our proprietary competitors (large international providers, mostly from the US), and in some cases even better. This also makes our code an attractive target.

We know many small providers around the world who offer their own products based on our open source solution. Larger ones sign contracts with us. Many comply with the licenses, others do not. Of course, this annoys us, but on the other hand, we prefer to put our energy into our project rather than engage in legal disputes somewhere in the world. But if a competitor goes too far, we take action. “Going too far” means changing copyright notices in our code and replacing our name with their own company name, ignoring attribution requirements, and violating open source licenses.

We have just successfully pursued such a case. We believe that the story is interesting for various groups: for open source developers, projects and companies, for people interested in legal issues (after all, we have set a legal precedent along the way – more on that later), and also for users of open source products and projects who are interested in the security of their supply chain.

There are essentially five things you need to successfully defend yourself against misuse: time, money, expertise, strong nerves, and a lot of patience. Expertise includes legal expertise, which means a good lawyer who is familiar with open source licenses. Of course, the jurisdiction in which you want to defend yourself is also a decisive factor, as you will always prefer the country in which your company is based, because this has several advantages that are also reflected in the costs. The law under which the case is heard is important. If you want to defend yourself internationally, you also need a law firm with the appropriate resources or network. Unless you are a large company with ample resources, you will not want to choose this route. We therefore conducted the proceedings discussed here in Germany, where our company is headquartered. Another part of the expertise is technical and forensic. After all, you must prove that your own code was used in the abusive application. If the other party does not fulfill its open source obligations and provide the source code, you must obtain the relevant code and prove that your share of it is part of the products that the other party is marketing. It is advisable to purchase the products through a third party to be able to provide proof. 

Once proof has been provided, the next steps are as follows: issue a warning letter and, if the manufacturer does not respond, obtain a preliminary injunction from the court. This prevents the products from being placed on the market until the defect (the abusive and unlicensed use of the software) has been remedied. In our case, the products were also distributed via hyperscaler platforms such as Microsoft Azure. Here, based on the Digital Services Act, the operator can be notified that licenses are being violated, which means that the products can no longer be distributed there because Microsoft (in the case of Azure) blocks them in the store if, for example, the preliminary injunction is pointed out there. This is a very good thing because it puts additional pressure on the product provider. Of course, this is only possible if you have plausible evidence, which can be quite a lot of work to obtain, depending on how much energy the product provider has expended to conceal the unlicensed use of third-party components. In our experience, advanced concealment techniques are used less frequently than expected: we were able to provide clear evidence both that the sources were ours and that it was not a mistake.

In our case, extensions were also linked to our libraries in violation of the copyleft. To conceal the license violation, our copyright notice was added to their own extensions. When we discovered these manipulations, we were naturally astonished at the audacity and immediately investigated further. We found that we were not the only victims of this provider but decided to focus on our own proceedings for the time being.

We had three goals when we started the project: to stop the misuse, to possibly obtain damages, and ultimately to impose the not inconsiderable costs of the proceedings on the other party. We have already achieved one goal: our injunction is legally binding and can no longer be appealed.

We have already achieved a significant legal victory in our proceedings, which has to do with the licensing of our product’s database content. Background: our solutions consist of three components: the application and system code and associated binaries, many thousands of test scripts for vulnerability detection, which together with information on already known vulnerabilities and input on how to fix them form a large database. This database is licensed for our community product under the Open Database Public License (ODbL). The ODbL allows a database to be freely copied, distributed, modified, and used (e.g., for your own applications or analyses). At the same time, it ensures that derived databases remain available under the same freedoms. The well-known geodatabase OpenStreetMap is licensed under the ODbL. Anyone who mixes an ODbL database with their own proprietary content must also place this modified database under the ODbL, which is therefore a copyleft license. In our case, an ODbL database was successfully defended in a license dispute for the first time in Germany. This resulted in a landmark decision that others can now refer to . We are very pleased about this.

And we are going even further: we have currently filed a lawsuit. This will deal with copyright and competition law issues, and will also address the issue of damages.

That sums up a process that has dragged on for several months and will continue into the future. If I were to draw a conclusion today, it would be a positive one: we have won on all important issues so far. We make open source stronger when we enforce its rules. Open source is a cornerstone of our business model, which is why it is important to us at to defend this foundation. On the other hand, the effort involved is considerable. Our business purpose is to provide our users with the greatest possible security for their IT infrastructure, not to engage in legal disputes. We only want to do this in a very measured way and only where the prospects of success are high and the framework conditions are favorable (as in our case here, where we can operate within the familiar legal system). We would like to thank our excellent legal representative, Dr. Till Jaeger from JBViniol, and the outstanding forensic expertise of DN-Systems – without their help, we would not have been able to achieve these successes.

We have a list of just over 100 suspected cases, and we regularly receive reports of such cases from partners, the community, and employees. The conditions are not always as favorable as in this case, and the relevance is not always great enough. Where this is the case, we will act against providers again, despite the considerable effort involved. We want a fair and healthy open source ecosystem, and particularly brazen violations – such as the one reported here – naturally trigger us. With this report, we also want to encourage others and – in keeping with the open source idea – share our knowledge.

Download
Regional Court Berlin II – Judgment, Case No. 15 O 299/25 (redacted version, English translation) – PDF

Kontakt Kostenlos testen Hier kaufen Zurück zur Übersicht