PT-2026-55584 · Go · Github.Com/Identrail/Identrail
CVE-2026-59185
·
Published
2026-07-03
·
Updated
2026-09-09
CVSS v3.1
8.5
High
| Vector | AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N |
Summary
identrail's GitHub App connection-completion endpoint binds a fully client-supplied
installation id to the caller's workspace without verifying that the installation belongs to, or was installed by, the workspace that initiated the connect flow. identrail then mints a GitHub App installation access token for the supplied installation id using the app's own JWT, so an authenticated tenant can link any other identrail customer's GitHub App installation into their own workspace and read that victim organization's private repositories.Affected code (default-on path, no feature flag)
- Route:
internal/api/router.go:3590—POST /v1/workspaces/:workspace id/projects/:project id/github/connect/complete.installation idis read from the JSON body or the attacker-controlledX-GitHub-Installation-IDheader (router.go:3582-3588). - Service:
internal/api/github connect.go:781CompleteGitHubConnection. Thestatetoken IS rigorously bound to the caller's scope (github connect.go:818:if stateRecord.TenantID != scope.TenantID || stateRecord.WorkspaceID != project.WorkspaceID || stateRecord.ProjectID != project.ProjectID { ... }), but the only check oninstallation idisrequest.InstallationID <= 0(:794). The raw client value is persisted as the workspace's connection (:840). - Cross-tenant read primitive:
internal/connectors/github/repositories.go:39ListInstallationRepositories→internal/connectors/github/app.go:170mints a token viaPOST /app/installations/{installationId}/access tokenssigned with the App JWT, succeeding for any installation where identrail's app is installed.
The feature-flagged V2 path
CompleteGitHubConnector (github connect.go:447, default off) shares the gap and is additionally weaker (matches pending connector by state value alone with no caller-scope re-check); a single fix should cover both.Intent proof
The code binds
state to {TenantID, WorkspaceID, ProjectID} and re-verifies it at completion (:818), demonstrating it understands binding is required. The asymmetry — state bound, installation id unbound — is the missed check.Exploitation
- Attacker is any authenticated identrail tenant; they call
StartGitHubConnectionfor their own workspace and receive astate. - Attacker calls the completion route with
{state: <their state>, installation id: V}where V is a victim org's identrail GitHub App installation id (installation ids are not secret — they appear in post-install redirect URLs, webhook payloads, the org's GitHub App settings, and are enumerable integers). CompleteGitHubConnectionaccepts (state matches attacker scope),ListInstallationRepositories(V)mints a token for V and lists the victim org's private repos, and the connection is persisted under the attacker's workspace.- Attacker now reads the victim org's private repository inventory and can drive posture scans/repo reads via their own workspace.
Impact: cross-tenant disclosure of another customer organization's private GitHub repositories and metadata.
Remediation
Bind
installation id with the same rigor as state: capture it from GitHub's signed post-install redirect (setup url/callback url) and pin it to the pending state at start time, and/or after minting verify the installation's account matches the org the initiating workspace is authorized for.Fix
Missing Authorization
IDOR
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Github.Com/Identrail/Identrail