UpHeron
All vulnerabilities

Servers and applications

GHSA-g333-hr44-g82p

AWS Bedrock Nodes Skip SSRF Protection for Custom Runtime Endpoints

Severity
Medium 5.3
Published
13 Nov 2026
Last changed
13 Nov 2026
Added to UpHeron
13 Nov 2026
Fixed in
2.47.6, 2.48.3, 3.2.2
Attack
Over the network · Needs a user account · No user action needed
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
Sources
Project advisories (GitHub)

Description

The AWS Bedrock Chat Model and Embeddings AWS Bedrock nodes let an AWS credential set a custom Bedrock runtime endpoint. Requests to that endpoint did not go through n8n's SSRF protection. A member who could create an AWS credential could point the endpoint at an internal or otherwise blocked address and make n8n send requests to it, and could see the start of the response in the node error.

From n8n-io/n8n's security advisory.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

  • Restrict n8n instance access to fully trusted users only.
  • Audit AWS credentials and remove any custom Bedrock Runtime Endpoint that is not expected.
  • Apply network-level controls to restrict outbound connections from the n8n host to internal addresses.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Workarounds as given by n8n-io/n8n's security advisory.

Affected software

SoftwareAffected versions
n8nServers and applications · github:n8n-io/n8n
  • Every version before 2.48.3
  • Every version before 2.47.6
  • Every version before 3.2.2

References