SAK T.E.CTechnology · Evaluation · Compliance Free domain checkCheck

Exploited vulnerabilities / CVE-2025-68613

Confirmed exploited · remote code execution · n8n

CVE-2025-68613

n8n remote code execution, confirmed exploited in the wild.

n8n contains an improper control of dynamically managed code resources vulnerability in its workflow expression evaluation system that allows for remote code execution.

99%chance of exploitation in the next 30 days (EPSS), 99th percentile
11 Maradded to CISA's Known Exploited Vulnerabilities list, 2026
25 Marfederal remediation deadline, already passed
Passedpast the deadline: patch now
CISA's name for itn8n Improper Control of Dynamically-Managed Code Resources Vulnerability
Vendor and productn8n · n8n
Typeremote code execution · CWE-913
ExploitedConfirmed by CISA listed 11 March 2026
Likelihoodone of the most likely to be exploited of every vulnerability tracked
Deadline25 March 2026 · already passed
Used in ransomwareNot reported
Advisoriesgithub.com ↗ · nvd.nist.gov ↗
What to do

Three steps, in this order

Step 1

Patch to the fixed version the vendor names, today if the product faces the internet.

Step 2

Until it is patched, take the affected service off the internet or put it behind a VPN or allow-list.

Step 3

Look for signs it was already used: new accounts, web shells, unexpected processes and outbound connections since the date it was listed.

CISA's required actionApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Is it on your estate?

Know before someone else finds it

Threat Landscape Monitoring fingerprints the software your internet-facing hosts disclose and matches it, every day, against this list and the exploitation scores. When a new entry touches something you run, you are told once, with the host and the fix. The free plan covers one domain.

Questions

CVE-2025-68613 in short

Is CVE-2025-68613 being exploited?

Yes. CISA added CVE-2025-68613 to its Known Exploited Vulnerabilities catalogue on 11 March 2026, which it does only on evidence of exploitation in the wild.

What is the CISA deadline for CVE-2025-68613?

US federal agencies must remediate it by 25 March 2026. Everyone else should treat that date as the latest safe point to patch an internet-facing system.

How likely is CVE-2025-68613 to be exploited in the next 30 days?

FIRST's Exploit Prediction Scoring System gives it 99%, the 99th percentile of every CVE it scores.

How do I fix CVE-2025-68613?

Patch to the fixed version the vendor names, today if the product faces the internet. Until it is patched, take the affected service off the internet or put it behind a VPN or allow-list. Look for signs it was already used: new accounts, web shells, unexpected processes and outbound connections since the date it was listed.

Sources: CISA Known Exploited Vulnerabilities catalogue (released 10 November 2026) and FIRST EPSS. Page compiled automatically by SAK T.L.M, the threat-intelligence tool of SAK T.E.C, on 13 November 2026.

Chat with us