Homepage

@n8n/config@1.65.2 vulnerabilities

  • latest version

    2.11.0

  • latest non vulnerable version

    2.11.0

  • first published

    1 years ago

  • latest version published

    5 days ago

  • licenses detected

  • View config package health on Snyk Advisor  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the @n8n/config package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • H
    Exposed Dangerous Method or Function

    Affected versions of this package are vulnerable to Exposed Dangerous Method or Function in the Code node when running in legacy JavaScript execution mode. An attacker can access or modify files on the host system with the same privileges as the application process by invoking internal helper functions from within the node. This is only exploitable if the instance is self-hosted, the legacy execution mode is enabled, and the attacker has authenticated workflow editing access.

    How to fix Exposed Dangerous Method or Function?

    Upgrade @n8n/config to version 2.0.0 or higher.

    <2.0.0
    • C
    Remote Code Execution (RCE)

    Affected versions of this package are vulnerable to Remote Code Execution (RCE) due to insufficient isolation in the Python Code Node that uses Pyodide. An authenticated attacker with permissions to create or modify workflows can execute arbitrary commands on the host system by creating or modifying workflows with malicious code.

    How to fix Remote Code Execution (RCE)?

    Upgrade @n8n/config to version 2.0.0-rc.1 or higher.

    <2.0.0-rc.1
    Go back to all versions of this package