Vulnerability in github.com/identrail/identrail (CVE-2026-59185)

Summary

Vulnerability in github.com/identrail/identrail (CVE-2026-59185). Risk of unauthorized operations or information disclosure. Exploitable via POST /v1/workspaces/. Mitigation: upgrade to 1.0.2 or later.

Original description

The description as published by the source.

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_id is read from the JSON body or the attacker-controlled X-GitHub-Installation-ID header (router.go:3582-3588).
Service: internal/api/github_connect.go:781 CompleteGitHubConnection. The state token 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 on installation_id is request.InstallationID <= 0 (:794). The raw client value is persisted as the workspace's connection (:840).
Cross-tenant read primitive: internal/connectors/github/repositories.go:39 ListInstallationRepositories → internal/connectors/github/app.go:170 mints a token via…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-59185 has been found in github.com/identrail/identrail.
Attackers can target a specific entry point like POST /v1/workspaces/ over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/identrail/identrail to 1.0.2 or later.
If unsure, ask your IT team or search "github.com/identrail/identrail CVE-2026-59185" on the vendor's site.

CVE-2026-59185 (github.com/identrail/identrail) — CWE-639
Attack surface: POST /v1/workspaces/ / POST /app/installations/{installationId}/access_tokens / installation_id / CompleteGitHubConnection
Patched: 1.0.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-639) exists in github.com/identrail/identrail. Attackers reach the vulnerable code path via POST /v1/workspaces/.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/identrail/identrail. Attack surface: POST /v1/workspaces/ / POST /app/installations/{installationId}/access_tokens / installation_id / CompleteGitHubConnection.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.0.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /v1/workspaces/ requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/identrail/identrail' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'github.com/identrail/identrail' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/identrail/identrail を grep し、稼働しているサービス・バージョンを把握する。
2
Hunt for indicators of compromise detect
```
grep 'POST /v1/workspaces/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'
```
アクセスログで POST /v1/workspaces/ への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
3
Apply patch patch
```
Upgrade github.com/identrail/identrail to 1.0.2
```
ステージング環境で 1.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
4
Post-deployment verification verify
```
Replay attack against POST /v1/workspaces/ on staging to confirm patch closes the vector
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/identrail/identrail

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.2"}]}]

Summary

Original description

Summary

Affected code (default-on path, no feature flag)

Auto-generated summary

Response actions

Affected packages

References