Use of hard-coded credentials in DataEase - #VU134825
Published: June 18, 2026
DataEase
Detailed vulnerability description
The vulnerability allows a remote attacker to access backend resources as the share creator.
The vulnerability exists due to use of a hardcoded cryptographic key in ShareSecretManage and TokenFilter when verifying linkToken values for passwordless shares. A remote attacker can forge a JWT signed with the hardcoded default key to access backend resources as the share creator.
Exploitation requires obtaining a passwordless share corresponding to a valid uid and resourceId pair.