Information Disclosure in github.com/kerberos-io/agent/machinery (CVE-2026-50192)
Summary
Vulnerability in github.com/kerberos-io/agent/machinery (CVE-2026-50192). Risk of unauthorized operations or information disclosure. Exploitable via POST /storage/upload. Mitigation: upgrade to 0.0.0-20260528173546-51f1a52e170f or later.
Original description
The description as published by the source.
Summary
The Kerberos Hub upload path sends the agent's Hub credentials in the custom X-Kerberos-Hub-PrivateKey and X-Kerberos-Hub-PublicKey request headers to the operator-configured Hub URL (config.HubURI). The HTTP client used (&http.Client{} in UploadKerberosHub) is constructed without a CheckRedirect policy, so it follows HTTP redirects automatically. Go's net/http strips only sensitive headers (Authorization, Cookie, WWW-Authenticate) on a cross-host redirect; it does not strip custom headers such as X-Kerberos-Hub-PrivateKey. As a result, if the configured HubURI returns a cross-host 30x redirect, the Hub private key is forwarded verbatim to the redirect target, disclosing the credential to an unintended third party (CWE-200 / CWE-522).
Impact
The Kerberos Hub private key (a long-lived secret authenticating the agent to Kerberos Hub) is leaked to an attacker-controlled host whenever the configured HubURI issues a cross-origin redirect. HubURI is operator configuration (models.Config.HubURI, JSON hub_uri); an open redirect on that host, a compromised/hijacked Hub deployment, a DNS/BGP hijack, or a malicious URL supplied in the agent config causes the secret to be exfiltrated. The leaked private key (together with the public key, which is forwarded in the same request) grants the attacker the agent's access to Kerberos Hub, including the ability to upload/impersonate the device.
Vulnerable code (file:line)
`machinery/sr…
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-50192 has been found in github.com/kerberos-io/agent/machinery.
Attackers can target a specific entry point like POST /storage/upload over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/kerberos-io/agent/machinery to 0.0.0-20260528173546-51f1a52e170f or later.
If unsure, ask your IT team or search "github.com/kerberos-io/agent/machinery CVE-2026-50192" on the vendor's site.
CVE-2026-50192 (github.com/kerberos-io/agent/machinery) — CWE-200
Attack surface: POST /storage/upload / GET /storage/upload / config.HubURI / UploadKerberosHub
Patched: 0.0.0-20260528173546-51f1a52e170f — 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.
Information disclosure (CWE-200) exists in github.com/kerberos-io/agent/machinery. Attackers reach the vulnerable code path via POST /storage/upload.
Check the vendor advisory for the affected versions of github.com/kerberos-io/agent/machinery. Attack surface: POST /storage/upload / GET /storage/upload / config.HubURI / UploadKerberosHub.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.0.0-20260528173546-51f1a52e170f.
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 /storage/upload requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/kerberos-io/agent/machinery' . 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/kerberos-io/agent/machinery' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/kerberos-io/agent/machineryを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /storage/upload' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /storage/uploadへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/kerberos-io/agent/machinery to 0.0.0-20260528173546-51f1a52e170fステージング環境で 0.0.0-20260528173546-51f1a52e170f に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /storage/upload on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web security-advisories@github.com
- web github.com