VulnWatch by ve1ve2
medium 4.3 EPSS 0.21%

GHSA-p9qq-6vpv-x7wj / CVE-2026-77173: Files Confidential tagging can be bypassed with # in filename

Source:
Nextcloud security advisories (GitHub nextcloud/security-advisories)
Published:
Fetched:
Updated:
Affects:
nextcloud Files Confidential

https://github.com/nextcloud/security-advisories/security/advisories/GHSA-p9qq-6vpv-x7wj ↗

repo-advisorynextcloudCWE-284securityrepo:nextcloud/security-advisories

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

Linked vulnerabilities (2)

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Files Confidential tagging can be bypassed with # in filename

CWE: CWE-284Aliases: CVE-2026-77173
CVE-2026-77173 medium 4.3 EPSS 0.21% (p12) NVDCVE.orgGHSA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Files Confidential tagging can be bypassed with # in filename

CWE: CWE-284Aliases: GHSA-p9qq-6vpv-x7wj