Homepage

@n8n/client-oauth2@1.12.0

  • latest version

    1.14.2

  • latest non vulnerable version

    1.15.0

  • first published

    3 years ago

  • latest version published

    5 days ago

  • licenses detected

  • View client-oauth2 package health on Snyk  (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/client-oauth2 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
    • M
    Incorrect Authorization

    Affected versions of this package are vulnerable to Incorrect Authorization in the OAuth 2.1 authorization. An attacker can gain unauthorized access to another user's workflow and execute it with the owner's credentials by registering an OAuth client and self-approving consent for a protected workflow. This allows the attacker to set inputs and read outputs, potentially exposing sensitive data from the owner's integrations.

    Note: This is only exploitable if the instance has at least one active workflow using an MCP Server Trigger node configured with OAuth2 authentication.

    How to fix Incorrect Authorization?

    Upgrade @n8n/client-oauth2 to version 1.11.2, 1.12.1 or higher.

    <1.11.2>=1.12.0 <1.12.1
    Go back to all versions of this package