| Title | SciPhi-AI R2R <=3.6.6 Hard-coded Credentials |
|---|
| Description | R2R signs and verifies HS256 session JWTs with R2R_SECRET_KEY. If that variable is unset or empty, both the bcrypt and NaCl crypto providers fall back to a secret hardcoded in the public source tree . Official Docker env files ship R2R_SECRET_KEY= empty, so default deployments use that constant. An unauthenticated attacker can mint a valid access token for any existing account, including the default superuser [email protected], and call authenticated APIs as that user. Enabling require_authentication does not fix this unless the secret is also changed. Password rotation does not invalidate tokens signed with the still-default HMAC key. |
|---|
| Source | ⚠️ https://gist.github.com/DReazer/6bc4f88053ec35f8358395bcc0d1a0bb |
|---|
| User | Snkn0w (UID 90071) |
|---|
| Submission | 08/26/2026 05:56 (1 month ago) |
|---|
| Moderation | 10/03/2026 20:05 (1 month later) |
|---|
| Status | Accepted |
|---|
| VulDB entry | 413372 [SciPhi-AI R2R up to 3.6.6 JWT Secret DEFAULT_BCRYPT_SECRET_KEY/DEFAULT_NACL_SECRET_KEY hard-coded credentials] |
|---|
| Points | 20 |
|---|