CVE-2025-41240: VMware bitnamicharts/appsmith · Exposed Files or Directories
Affects VMware bitnamicharts/appsmithSource CVE Database V5
Not known to be exploited · CVSS 10.0 Critical.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubbitnami/charts/appsmithpkg:github/bitnami/charts/appsmithOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-41240, organizations should take the following specific actions: 1) Immediately audit all deployments of bitnamicharts/appsmith Helm charts to identify those using version 21.2.0 with the default usePasswordFiles=true setting. 2) Modify the Helm chart configuration to disable usePasswordFiles or change the mounting path of secrets to a location outside the web server document root to prevent HTTP/S access. 3) Implement strict network policies and ingress controls to restrict external access to the affected applications, limiting exposure to trusted internal networks only. 4) Rotate all Kubernetes Secrets and any credentials that may have been exposed to reduce the risk of compromise. 5) Monitor application logs and network traffic for suspicious access patterns targeting the secrets paths. 6) Stay alert for vendor patches or updated Helm chart releases addressing this vulnerability and apply them promptly. 7) Employ Kubernetes best practices for secret management, such as using encrypted secrets, RBAC restrictions, and avoiding mounting secrets in publicly accessible paths. 8) Conduct regular security assessments and penetration tests to detect similar misconfigurations in Kubernetes deployments.
Description
Three Bitnami Helm charts mount Kubernetes Secrets under a predictable path (/opt/bitnami/*/secrets) that is located within the web server document root. In affected versions, this can lead to unauthenticated access to sensitive credentials via HTTP/S. A remote attacker could retrieve these secrets by accessing specific URLs if the application is exposed externally. The issue affects deployments using the default value of usePasswordFiles=true, which mounts secrets as files into the container filesystem.