Release v2.0
Appsmith 2.0 includes major dependency upgrades to MongoDB 7, Java 25, and Node 24, along with numerous security fixes and bug fixes. Users upgrading from versions before v1.96 must first upgrade to v1.99 to complete required database migrations before proceeding to 2.0+.
If you are upgrading from a version earlier than v1.96, you must first upgrade to version v1.99 before upgrading to 2.0+.
This requirement is especially important for instances using the built-in MongoDB. Appsmith 2.0 bundles MongoDB 7, and versions v1.96 through v1.99 include the required migration changes needed to support this upgrade path.
Skipping this intermediate upgrade will cause the upgrade to 2.0+ to fail, including installations using an external MongoDB instance. Completing this step is required for all deployments.
If you already attempted the upgrade and encountered a failure, no data loss or destructive changes will occur. Simply upgrade to version v1.99 first. Once the instance is successfully running on v1.99, you can proceed with upgrading to 2.0+.
For detailed upgrade instructions, see:
https://docs.appsmith.com/getting-started/setup/instance-management/update-appsmith
Features
- Added a documentation link tooltip for the Appsmith Base URL setting and implemented trailing-slash normalization. (#41782)
- Added support for the MongoDB Operator in Helm deployments. (#41733)
- Added Ask AI CE stubs and shared file wiring support. (#41692)
Fixes
- Validated request origins before persisting invited users. [APP-15239] (#41826)
- Preserved Redis credentials during
appsmithctl restore. (#41827) - Upgraded
postgresql-jdbcto42.7.11to remediate CVE-2026-42198. (#41812) - Added validation for Git repository URLs. (#41819)
- Prevented unauthenticated access to full OpenAPI documentation. (GHSA-v6jh-fx3m-7xhw) (#41803)
- Fixed a path traversal vulnerability. (GHSA-m4hv-9p7g-56vm) (#41790)
- Upgraded
arangodb-java-driverto7.25.0to remediate CVE-2025-52999. (#41789) - Replaced generic “Response not valid” messages with more actionable error messages for improved observability. (#41769)
- Failed closed for token-bearing emails when
APPSMITH_BASE_URLis unset. (GHSA-j9gf-vw2f-9hrw) (#41767) - Updated Helm charts to use documented image values instead of the undocumented
_imagekey. (#41765) - Fixed a datasource configuration leak in Appsmith App Viewer imports. (GHSA-93mf-9h52-gfxp) (#41764)
- Prevented stored XSS via SQL autocomplete. (GHSA-vjfq-fvfc-3vjw) (#41760)
- Stripped identity fields from imported JSON before persistence. (#41761)
- Prevented HTML entity decoding from corrupting binary file uploads in multipart form data. (#41742)
- Pinned
protobufjsto^7.5.5to address GHSA-xq3m-2v4x-88gg. (#41745) - Upgraded
axiosto1.15.0to address GHSA-3p68-rc4w-qgx5. (#41739) - Upgraded bundled Mongo to 7.x
- Upgraded backend JAVA to 25.x
- Upgraded backed Node to 24.x
- Upgraded bundled MongoDB to 7.x
Source: original entry ↗
More from Appsmith
Follow Appsmith to get its new changes in your feed and email digest.
Release v2.5.0
Appsmith v2.5.0 includes security patches for bundled dependencies, stricter datasource credential handling and permission checks, schema updates for Git-connected applications with potential breaking changes to Elasticsearch bindings, and new features like application descriptions, list widget selection controls, and enhanced table column formatting. Appsmith AI reached end-of-life on September 30, 2026 and can no longer be used.
Release v2.4.3
Appsmith v2.4.3 includes end-of-life notice for Appsmith AI (September 30, 2026), security updates for bundled dependencies, improved error message handling in action executions, and UI enhancements like font controls in Rich Text Editor and restored search/filtering in Table widgets.
Release v2.4.2
Appsmith v2.4.2 includes security updates for bundled dependencies including Bouncy Castle, fixes for page cloning performance to prevent memory exhaustion, improved UI consistency for Ask AI and OAuth2 fields, and enhancements to Git and deployment tools. Appsmith AI reaches end-of-life on September 30, 2026, and users must migrate to direct provider datasources.