GHSA-p9qq-6vpv-x7wj / CVE-2026-77173: Files Confidential tagging can be bypassed with # in filename
- Published:
- Fetched:
- Updated:
- Affects:
- nextcloud Files Confidential
https://github.com/nextcloud/security-advisories/security/advisories/GHSA-p9qq-6vpv-x7wj ↗
Files Confidential tagging can be bypassed with # in filename ### Impact A user could create a docx or odt file with a `#` in the filename with confidential information such as a credit card number and have it not be marked as confidential. ### Patches It is recommended that the Nextcloud files_confidential app is upgraded to 3.3.1, 4.1.1 or 5.1.0 ### Workarounds * Change config setting: Add `#` to `forbidden_filename_characters` and rename all affected files ### References * [HackerOne](https://hackerone.com/reports/3682163) * [PullRequest](https://github.com/nextcloud/files_confidential/pull/262) ### For more information If you have any questions or comments about this advisory: * Create a post in [nextcloud/security-advisories](https://github.com/nextcloud/security-advisories/discussions) * Customers: Open a support ticket at [portal.nextcloud.com](https://portal.nextcloud.com) Affected packages: nextcloud:Files Confidential Patched: Files Confidential 3.3.1, 4.1.1, 5.1.0