Called exploited 64 days after disclosure.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listing2mo
- Last KEV listing18d
- Last sighting6mo
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Mar 11, 2026
- EUVDENISA, European Unionlisted Mar 11, 2026
- VulnCheck KEVcommercial researchlisted Feb 21, 2026
- CIRCLaggregator, mirrors the abovelisted Mar 11, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationexpel.com/blog/the-ai-cve-exploitation-evidence-story-headli
- reported exploitationwww.tenable.com/blog/the-agentic-ai-threat-cluster-seven-inc
- reported exploitationunit42.paloaltonetworks.com/autonomous-ai-cyber-attack-campa
- reported exploitationview.bitsight.com/viewer/275c18689811d887dfa0368866323ed5#1
- reported exploitationwww.recordedfuture.com/blog/march-2026-cve-landscape
- reported exploitationapi.vulncheck.com/v3/index/vulncheck-canaries?cve=CVE-2025-6
12 public reports collected from VulnCheck and CIRCL, first on Feb 21, 2026. Each links to its original source. We have not verified them.
Description
n8n contains an improper control of dynamically managed code resources vulnerability in its workflow expression evaluation system that allows for remote code execution.
Required action (CISA)
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
