<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/comments/feed</id>
  <title>Most recent comments.</title>
  <updated>2026-09-17T09:52:34.653346+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent comments.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/comment/10eccd79-ce3d-4273-b399-d535e160f2c9</id>
    <title>UAC-0001 (APT28) carries out cyberattacks against Ukraine and EU countries using the exploit CVE-2026-21509</title>
    <updated>2026-09-17T09:52:34.656911+00:00</updated>
    <author>
      <name>Paul Jung</name>
      <uri>https://vulnerability.circl.lu/user/Thanat0s</uri>
    </author>
    <content>On 26 January 2026, Microsoft disclosed the actively exploited vulnerability CVE-2026-21509 in Microsoft Office, and within days weaponized DOC files appeared in public and via phishing campaigns targeting Ukrainian and EU government entities, using lures related to Ukraine and EU COREPER meetings; opening the documents triggers a WebDAV-based infection chain that downloads an LNK file, deploys a malicious DLL through COM hijacking and explorer.exe restart, executes shellcode hidden in an image, and ultimately launches the COVENANT command-and-control framework, which leverages the legitimate Filen cloud infrastructure, indicating a coordinated campaign likely to expand rapidly due to delayed patching and limited adoption of mitigations.

[https://cert.gov.ua/article/6287250](https://cert.gov.ua/article/6287250)</content>
    <link href="https://vulnerability.circl.lu/comment/10eccd79-ce3d-4273-b399-d535e160f2c9"/>
    <published>2026-02-02T13:04:42.083484+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/comment/d766d344-c029-419a-b990-fb512e9cb929</id>
    <title>The Ni8mare Test: n8n RCE Under the Microscope (CVE-2026-21858)</title>
    <updated>2026-09-17T09:52:34.659572+00:00</updated>
    <author>
      <name>Alexandre Dulaunoy</name>
      <uri>https://vulnerability.circl.lu/user/adulau</uri>
    </author>
    <content>Interesting statement from this article  Horizon3.ai has seen no evidence of customers using vulnerable configurations of n8n, even if the versions in use are within the vulnerable range. While the vulnerability exists, certain pre-requisites will limit widespread exploitability."


- [The Ni8mare Test: n8n RCE Under the Microscope (CVE-2026-21858)](https://horizon3.ai/attack-research/attack-blogs/the-ni8mare-test-n8n-rce-under-the-microscope-cve-2026-21858/)


Trendy vulnerabilities aren’t always worth the hype—panic-driven responses often lead to wasted time and resources. This is top of mind for us as we’ve researched recent issues regarding n8n, a popular AI workflow automation tool. After assessing relevant data from customer’s production environments, Horizon3.ai’s Attack Team determined that the blast radius of CVE-2026-21858 is not as large as initially claimed:

 - n8n Unauthenticated Remote Code Execution aka Ni8mare vulnerability (CVE-2026-21858) garnered attention regarding the RCE potential, but Horizon3.ai determined that no customer instances are impacted, even those running vulnerable versions.

Whenever a new vulnerability surfaces and makes headlines, organizations are left scrambling to determine whether they’re at risk. Failing to do so introduces major exposure if a vulnerability does turn out to be critical. But with a myriad of security products misleading users with claims of hundreds of critical installations, teams are left overwhelmed with what to fix, what to fix first, and most critically, why. Let’s dive into what we know about this latest trending vulnerability.</content>
    <link href="https://vulnerability.circl.lu/comment/d766d344-c029-419a-b990-fb512e9cb929"/>
    <published>2026-01-12T07:45:18.353778+00:00</published>
  </entry>
</feed>
