CVE-2026-56777

MEDIUMPre-NVD 5.05.0—
EchelonGraph scoreMEDIUM confidence

Score 5.0 from GitHub Security Advisory published 2026-07-01. a secondary CVSS source baseline 5.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

n8n before 2.25.7 and 2.26.x before 2.26.2 contains an abstract syntax tree (AST) security validator bypass in the Python Code node. An authenticated user with permission to create or modify workflows containing a Python Code node can bypass the validator and access the task executor module namespace. The issue only affects self-hosted instances where the Python Task Runner is enabled; where N8N_BLOCK_RUNNER_ENV_ACCESS is configured to allow it, this can disclose environment variables accessible to the task runner process.

CVSS v3
5.0
EG Score
5.0(medium)
EG Risk
27(Track)
EG Risk 27/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity50% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (2)

Auto-updated Jul 3, 2026
Patch available. Sources: github.
generic

n8n - AST Validator Bypass in Python Code Node | Advisories | VulnCheck

https://www.vulncheck.com/advisories/n8n-ast-validator-bypass-in-python-code-node
github Patch Available

Python Code Node AST Validator Bypass · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-jwm3-qcfw-c5pp

Vendor Advisories for CVE-2026-56777(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
n8n—2.25.7—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 82× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 147 total refreshes for this CVE.

  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-25 04:23 UTCEG score recompute
  4. 2026-08-25 04:22 UTCGHSA enrichment
  5. 2026-08-24 05:25 UTCGHSA enrichment
  6. 2026-08-23 06:28 UTCEG score recompute
  7. 2026-08-23 06:28 UTCGHSA enrichment
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 07:30 UTCEG score recompute
  10. 2026-08-22 07:30 UTCGHSA enrichment
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-21 04:41 UTCEG score recompute
  13. 2026-08-21 04:41 UTCGHSA enrichment
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-20 04:53 UTCEG score recompute
  16. 2026-08-20 04:53 UTCGHSA enrichment
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 22:54 UTCEG score recompute
  19. 2026-08-18 22:54 UTCGHSA enrichment
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-17 23:40 UTCEG score recompute
  22. 2026-08-17 23:40 UTCGHSA enrichment
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-16 19:51 UTCEG score recompute
  25. 2026-08-16 19:51 UTCGHSA enrichment
Show 75 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 02:14 UTCEPSS rescore
  3. 2026-08-15 20:03 UTCEG score recompute
  4. 2026-08-15 20:03 UTCGHSA enrichment
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 21:04 UTCGHSA enrichment
  7. 2026-08-13 22:07 UTCEG score recompute
  8. 2026-08-13 22:07 UTCGHSA enrichment
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-12 23:11 UTCEG score recompute
  11. 2026-08-12 23:11 UTCGHSA enrichment
  12. 2026-08-12 13:51 UTCEPSS rescore
  13. 2026-08-12 00:14 UTCEG score recompute
  14. 2026-08-12 00:14 UTCGHSA enrichment
  15. 2026-08-11 01:17 UTCEG score recompute
  16. 2026-08-11 01:17 UTCGHSA enrichment
  17. 2026-08-11 00:00 UTCEPSS rescore
  18. 2026-08-10 02:21 UTCEG score recompute
  19. 2026-08-10 02:21 UTCGHSA enrichment
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 03:24 UTCEG score recompute
  22. 2026-08-09 03:24 UTCGHSA enrichment
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-08 04:28 UTCEG score recompute
  25. 2026-08-08 04:28 UTCGHSA enrichment
  26. 2026-08-07 05:31 UTCEG score recompute
  27. 2026-08-07 05:31 UTCGHSA enrichment
  28. 2026-08-06 13:47 UTCEPSS rescore
  29. 2026-08-06 06:34 UTCEG score recompute
  30. 2026-08-06 06:34 UTCGHSA enrichment
  31. 2026-08-05 19:17 UTCEPSS rescore
  32. 2026-08-05 07:38 UTCEG score recompute
  33. 2026-08-05 07:38 UTCGHSA enrichment
  34. 2026-08-04 15:10 UTCEPSS rescore
  35. 2026-08-04 10:39 UTCEPSS rescore
  36. 2026-08-04 08:40 UTCEG score recompute
  37. 2026-08-04 08:40 UTCGHSA enrichment
  38. 2026-08-03 10:36 UTCEPSS rescore
  39. 2026-08-03 08:06 UTCGHSA enrichment
  40. 2026-08-02 09:08 UTCEG score recompute
  41. 2026-08-02 09:08 UTCGHSA enrichment
  42. 2026-08-02 02:27 UTCEPSS rescore
  43. 2026-08-01 10:12 UTCEG score recompute
  44. 2026-08-01 10:12 UTCGHSA enrichment
  45. 2026-08-01 04:16 UTCEPSS rescore
  46. 2026-07-31 11:15 UTCEG score recompute
  47. 2026-07-31 11:15 UTCGHSA enrichment
  48. 2026-07-30 16:28 UTCEPSS rescore
  49. 2026-07-30 12:17 UTCEG score recompute
  50. 2026-07-30 12:17 UTCGHSA enrichment
  51. 2026-07-30 01:30 UTCEPSS rescore
  52. 2026-07-30 01:30 UTCEPSS rescore
  53. 2026-07-29 12:56 UTCEG score recompute
  54. 2026-07-29 12:56 UTCGHSA enrichment
  55. 2026-07-28 15:37 UTCEPSS rescore
  56. 2026-07-28 13:59 UTCEG score recompute
  57. 2026-07-28 13:59 UTCGHSA enrichment
  58. 2026-07-27 14:14 UTCEPSS rescore
  59. 2026-07-27 12:28 UTCEG score recompute
  60. 2026-07-27 12:28 UTCGHSA enrichment
  61. 2026-07-26 14:54 UTCEPSS rescore
  62. 2026-07-26 14:54 UTCEPSS rescore
  63. 2026-07-26 13:31 UTCEG score recompute
  64. 2026-07-26 13:31 UTCGHSA enrichment
  65. 2026-07-25 14:18 UTCEPSS rescore
  66. 2026-07-25 14:18 UTCEPSS rescore
  67. 2026-07-24 14:18 UTCEPSS rescore
  68. 2026-07-24 14:18 UTCEPSS rescore
  69. 2026-07-23 14:18 UTCEPSS rescore
  70. 2026-07-23 03:20 UTCEG score recompute
  71. 2026-07-22 14:08 UTCEPSS rescore
  72. 2026-07-21 15:25 UTCEPSS rescore
  73. 2026-07-20 17:08 UTCEPSS rescore
  74. 2026-07-19 14:31 UTCEPSS rescore
  75. 2026-07-19 14:31 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-56777?
CVE-2026-56777 is a medium vulnerability published on July 1, 2026. n8n before 2.25.7 and 2.26.x before 2.26.2 contains an abstract syntax tree (AST) security validator bypass in the Python Code node. An authenticated user with permission to create or modify workflows containing a Python Code node can bypass the validator and access the task executor module…
When was CVE-2026-56777 disclosed?
CVE-2026-56777 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56777 actively exploited?
CVE-2026-56777 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 75.0% of all scored CVEs.
What is the CVSS score of CVE-2026-56777?
CVE-2026-56777 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2026-56777?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56777, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56777

Explore →

Is Your Infrastructure Affected by CVE-2026-56777?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs