| Title | harnessrouter >= 0.4.2, < 0.31.11 Authentication Bypass Issues |
|---|
| Description | The gateway's identity mode (HR_IDENTITY_MODE) decides how it treats a request that carries the internal key beside a sign-in token. Left unset, it defaulted to observe, which keeps the X-Harness-Org and X-Harness-Member headers the request asserts even when the token does not verify. A console that is not in self-hosted mode attaches the internal key to every request carrying an Authorization header, so on a deployment serving several organizations that left the mode unset, a made-up token with a made-up organization header was answered as that organization. |
|---|
| Source | ⚠️ https://github.com/HarnessRouter/harnessrouter/security/advisories/GHSA-qrr8-m92f-7vfp |
|---|
| User | mikannse (UID 100854) |
|---|
| Submission | 10/08/2026 03:47 (14 days ago) |
|---|
| Moderation | 10/21/2026 11:01 (13 days later) |
|---|
| Status | Accepted |
|---|
| VulDB entry | 424708 [HarnessRouter up to 0.31.10 Identity Mode gateway/app.py X-Harness-Org/X-Harness-Member improper authorization] |
|---|
| Points | 20 |
|---|