Open Redirect in github.com/concourse/concourse (CVE-2026-49826)
Summary
Vulnerability in github.com/concourse/concourse (CVE-2026-49826). Risk of unauthorized operations or information disclosure. Exploitable via url. Mitigation: upgrade to 8.2.3 or later.
Original description
The description as published by the source.
Concourse login flow has an open redirect issue in github.com/concourse/concourse
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-49826 has been found in github.com/concourse/concourse.
Attackers can target a specific entry point like url over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/concourse/concourse to 8.2.3 or later.
If unsure, ask your IT team or search "github.com/concourse/concourse CVE-2026-49826" on the vendor's site.
CVE-2026-49826 (github.com/concourse/concourse) — CWE-601
Attack surface: url / RawPath / Path / example.com
Patched: 8.2.3 — 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.
A vulnerability (CWE-601) exists in github.com/concourse/concourse. Attackers reach the vulnerable code path via url.
Check the vendor advisory for the affected versions of github.com/concourse/concourse. Attack surface: url / RawPath / Path / example.com.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 8.2.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/concourse/concourse' . 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
-
1Identify exposure identify
grep -r 'github.com/concourse/concourse' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/concourse/concourseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/concourse/concourse to 8.2.3ステージング環境で 8.2.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com
- web nvd.nist.gov