# CVE-2026-50192: Kerberos Hub private key (X-Kerberos-Hub-PrivateKey) leaked to cross-host redirect target due to redirect-following HTTP client without CheckRedirect

> Kerberos Agent leaks private hub credentials to third-party redirect targets due to missing redirect checks, allowing attackers to intercept sensitive authentication keys.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-h5gx-45rj-2h5j, GO-2026-5890

## What is CVE-2026-50192?

CVE-2026-50192 is a medium-severity vulnerability in kerberos-io agent, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Kerberos Agent is an open source video (surveillance) management agent. Prior to version 3.6.26, 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. Version 3.6.26 fixes the issue by implementing the `CheckRedirect` strip plus a cross-host regression test is provided to the maintainer through the advisory's private temporary fork.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-50192?

3 open source packages ship an affected version, including github.com/kerberos-io/agent/machinery.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/kerberos-io/agent/machinery` | Go | All versions | 0.0.0-20260528173546-51f1a52e170f |
| `github.com/kerberos-io/agent/machinery` | Go | All versions | 0.0.0-20260528173546-51f1a52e170f |
| `github.com/kerberos-io/agent/machinery` | Go | All versions | 0.0.0-20260528173546-51f1a52e170f |

## How do I fix CVE-2026-50192?

Upgrade github.com/kerberos-io/agent/machinery to 0.0.0-20260528173546-51f1a52e170f or later.

## Is CVE-2026-50192 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50192 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50192 and fix it if it is affected.

What it is: CVE-2026-50192 is a medium-severity vulnerability in kerberos-io agent, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50192 exists.

Affected packages and fixed versions:
- github.com/kerberos-io/agent/machinery (Go): affected all versions; fixed in 0.0.0-20260528173546-51f1a52e170f
- github.com/kerberos-io/agent/machinery (Go): affected all versions; fixed in 0.0.0-20260528173546-51f1a52e170f
- github.com/kerberos-io/agent/machinery (Go): affected all versions; fixed in 0.0.0-20260528173546-51f1a52e170f

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50192/ (Markdown: https://insights.sbomify.com/CVE-2026-50192/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50192
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50192
- OSV: https://osv.dev/vulnerability/CVE-2026-50192

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50192/
Summaries are generated and may contain mistakes; the official description above is the record.