CVE-2026-25115
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedn8n is an open source workflow automation platform. Prior to version 2.4.8, a vulnerability in the Python Code node allows authenticated users to break out of the Python sandbox environment and execute code outside the intended security boundary. This issue has been patched in version 2.4.8.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA sandbox escape vulnerability in n8n's Python Code node allows authenticated users to break out of the Python sandbox environment and execute arbitrary code outside the intended security boundary, potentially leading to full system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.4.8CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify n8n versionAccess n8n via web UI and check the version in Settings > About, or run `npm list n8n` if installed via npm, or check the Docker image tag if containerizedAffected if Version is below 2.4.8 (e.g., 2.4.7, 2.3.0, etc.)
-
Verify Python Code node is availableNavigate to the n8n workflow editor and check if the Python Code node appears in the node list, or check Settings > Nodes > Python CodeAffected if Python Code node is present and enabled in the instance
-
Confirm user access to Python Code nodeReview which user roles or API keys have access to create or edit workflows containing the Python Code node, or check if the node is visible to non-admin usersAffected if Regular authenticated users (non-admin) can access or execute the Python Code node
You are affected if your n8n instance runs version below 2.4.8 AND the Python Code node is enabled and accessible to users beyond trusted administrators.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.4.8
Upgrade n8n to version 2.4.8 or later to patch the vulnerability. Until then, restrict access to the Python Code node to only trusted, necessary users.
n8n version 2.4.8
- Stop the n8n service before performing the upgrade
- Backup your n8n instance data, workflows, and configurations
- Upgrade n8n to version 2.4.8 or later using your installation method (e.g., Docker: 'docker pull n8nio/n8n:latest' then recreate container, or npm: 'npm install -g n8n@latest')
- After upgrading, verify the new version is running: check n8n startup logs or visit the UI and confirm the version number
- Restart any dependent services that connect to n8n
- Test that the Python Code node functions correctly in workflows after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25115 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25115 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data