Vulnerability in github.com/zalando/skipper (CVE-2026-50197)
Summary
Vulnerability in github.com/zalando/skipper (CVE-2026-50197). Confidential information can be exposed externally. Exploitable via POST /priv. Mitigation: upgrade to 0.26.10 or later.
Original description
The description as published by the source.
Skipper is an HTTP router and reverse proxy for service composition. Prior to 0.26.10, zalando/skipper's OpenPolicyAgent integration silently bypasses request-body inspection on HTTP/1.1 Transfer-Encoding: chunked and HTTP/2 requests that omit the content-length pseudo-header, because the opaAuthorizeRequestWithBody filter and OpenPolicyAgentInstance.ExtractHttpBodyOptionally in filters/openpolicyagent/openpolicyagent.go produce an empty raw_body and input.parsed_body while the upstream service receives the full attacker-controlled body. This issue is fixed in version 0.26.10.
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-50197 has been found in github.com/zalando/skipper.
Attackers can target a specific entry point like POST /priv over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade github.com/zalando/skipper to 0.26.10 or later.
If unsure, ask your IT team or search "github.com/zalando/skipper CVE-2026-50197" on the vendor's site.
CVE-2026-50197 (github.com/zalando/skipper) — CWE-444
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /priv / opaAuthorizeRequestWithBody / raw_body / input.parsed_body
Patched: 0.26.10 — 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-444) exists in github.com/zalando/skipper. Attackers reach the vulnerable code path via POST /priv without authentication.
Check the vendor advisory for the affected versions of github.com/zalando/skipper. Attack surface: POST /priv / opaAuthorizeRequestWithBody / raw_body / input.parsed_body.
Severity: ?. Confidential information can be exposed externally.
Update to 0.26.10.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /priv requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/zalando/skipper' . 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/zalando/skipper' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/zalando/skipperを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /priv' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /privへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/zalando/skipper to 0.26.10ステージング環境で 0.26.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /priv on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com