You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bug: Personal Vault stores plaintext passwords and allows unsafe note paths #15759
The app uses a local users.json file and standard library modules only. No dependency list was provided for the sample application.
Expected behavior
The Personal Vault application should not store passwords in plaintext, and note filenames should be validated before being used to construct filesystem paths. The login flow should verify credentials securely and user note operations should remain confined to the current vault directory.
Actual behavior
The sample application stores each password in users.json as plaintext and compares it directly during login. It accepts arbitrary note names and uses them to build paths under the user's vault without validating or normalizing them. This can allow credential disclosure and filesystem access outside the intended vault directory, and file operations can crash or behave unexpectedly when an invalid path is used.
Hi! I’d love to help resolve this issue and contribute to the project.
I have reviewed the repository guidelines and set up the project locally.
Could you please assign this issue to me?
Let me know if there are any specific edge cases or requirements I should keep in mind!
Activity
pawangopallavudya-commits commentedon Nov 17, 2026
Hi! I’d love to help resolve this issue and contribute to the project.
I have reviewed the repository guidelines and set up the project locally.
Could you please assign this issue to me?
Let me know if there are any specific edge cases or requirements I should keep in mind!