Skip to main content

Changelog

Updates, changes, and improvements at Retool.

5 posts tagged with "Security"

View All Tags

Self-hosted deployments require a container running the code-executor service

Andrew Guan
Security Engineer

Beginning in version 3.251.0, a container running code-executor is required to run workflows and custom API authentication. Previously, these features could be run in a sandbox in the backend container. Retool's security team has become aware of a sandbox escape and will no longer be supporting sandboxing in the backend. For more information refer to the disclosure page.

Removal of image download functionality for external app users

Julie Chen
Deployed Performance Engineer

These features are no longer available on Retool Cloud and Self-hosted Retool 3.114 or later.

Due to potential security concerns, Retool is removing certain functionality that enables external app users to download images. No security breach or active vulnerability has occurred, and you do not need to take any security-specific actions.

External and embedded, publicly available apps will no longer support:

  • Download Image columns in the Legacy Table component. Use an alternative method, such as a Link or Button column type, for image URL links. Retool strongly recommends you migrate to the current Table component instead.
  • Export PDFs with images hosted on separate domains. All other components will be included in the PDF export. Retool recommends moving your publicly-hosted images to be hosted on the same domain as your Retool instance. For example, you could use images that are natively uploaded to the Image component, stored in Retool Storage, stored in Retool Database, Base64-encoded, or stored in an Amazon S3 bucket.