@n8n/n8n-nodes-langchain@2.27.2
latest version
2.33.3
latest non vulnerable version
first published
2 years ago
latest version published
3 days ago
licenses detected
- >=0
Direct Vulnerabilities
Known vulnerabilities in the @n8n/n8n-nodes-langchain 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| Vulnerability | Vulnerable Version |
|---|---|
Affected versions of this package are vulnerable to Incorrect Authorization via the Note: This is only exploitable if workflow sharing is enabled and the attacker has been explicitly granted Editor access to a shared workflow, and knows the target credential's ID. How to fix Incorrect Authorization? Upgrade | <1.122.46>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1 |
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in the Note: This is only exploitable if SSRF protection is enabled and the attacker has permissions to create or edit workflows. How to fix Server-side Request Forgery (SSRF)? Upgrade | <2.31.3>=2.32.0 <2.32.1 |
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 | >=2.27.0 <2.29.7>=2.30.0 <2.30.1 |
