Security context

What an agent needs to avoid regressing past fixes and find the next vuln in this repo.

kubernetes-client/python
master @ ffd05cd
3
Fixes
0
CVEs
HIGH
Peak severity
33.3%
Coverage
Highlights
Auth Bypass: 2 prior fixes. Scrutinize any change in this area.
config/kube_config.py: most-fixed (1 issue). Treat as high-risk during review.
3 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns

The bug types that recur here, drawn from past fixes, not open vulnerabilities.

Auth Bypass: The API key prefix lookup could miss the legacy 'authorization' alias, causing the 'Bearer ' prefix to be omitted and leading to authentication bypass. The fix added a fallback but sibling paths may still lack it.
Auth Bypass: Exec-based auth tokens could go stale without a refresh hook, allowing unauthorized access with expired credentials. The fix added an expiry check, but other credential sources (e.g., token files) may not have equivalent refresh logic.
Dependency Vulnerability: A subproject reference pinned an outdated yaml library with a known vulnerability. Supply-chain risk persists if other subproject references or dependency pins are not regularly updated.