Skip to content

Repository navigation

Arbitrary file read and write via symlinks in Git import

Critical
wyattwalter published GHSA-fqwc-g9wm-5895 Oct 6, 2026

Package

maven com.appsmith:appsmith-git (Maven)

Affected versions

<= 2.2

Patched versions

2.3

Description

Summary

An authenticated Appsmith user can commit a symlink inside a Git repository that, when imported or committed through Appsmith's Git integration, causes the server to follow the link outside the intended directory. This affects Appsmith Community and Enterprise self-hosted deployments using the Git import or commit feature, which is part of the default installation.

Impact

An attacker can read arbitrary files on the server, including credential material such as datasource passwords and the instance's encryption key, and can write arbitrary files that the server process later executes, resulting in code execution with the server process's privileges. No special role or admin access is required beyond an authenticated account, and self-registration is enabled by default in Appsmith Community Edition.

Affected and patched versions

Appsmith versions before 2.3 are affected. Upgrade to 2.3 or later.

Workarounds

Disable self-registration and restrict who can create accounts, since any authenticated user can exploit this issue through the Git import or commit feature.

After upgrading

Rotate the instance's encryption password and salt, and any datasource credentials, if you suspect this issue was exploited before upgrading.

Credits

Thanks to Rahul Maini (@iamnoooob) at Hacktron and @123vivekr for reporting this issue.

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

CVE ID

No known CVE

Weaknesses

Improper Link Resolution Before File Access ('Link Following')

The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. Learn more on MITRE.

Credits