Server-Side Request Forgery (SSRF) Affecting n8n-oci-entrypoint package, versions <2.33.4-r0


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.17% (7th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-N8NOCIENTRYPOINT-19503656
  • published3 Sept 2026
  • disclosed20 Aug 2026

Introduced: 20 Aug 2026

NewCVE-2026-77069  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

Upgrade Minimos:latest n8n-oci-entrypoint to version 2.33.4-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream n8n-oci-entrypoint package and not the n8n-oci-entrypoint package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

n8n before 1.123.69, 2.33.4, and 2.34.1 contains an SSRF protection bypass in the OAuth2 credential authorization-code-to-access-token exchange. While OAuth2 discovery and dynamic-client-registration requests use n8n's SSRF-protected HTTP client, the token exchange uses a separate client with no SSRF guard. A user with credential-creation permissions can set the access-token URL to an internal address and complete the OAuth2 flow, causing n8n to send a fixed-shape token-exchange POST to that target and reflect its response body back to the attacker (limited to what the target returns to this specific request).

CVSS Base Scores

version 3.1