Access Restriction Bypass in kubernetes
Published Feb 3, 2016 · Updated Oct 23, 2026 · Also known as GHSA-xx8c-m748-xr4j, GO-2022-0893
Original summary
Normalized public record · Updated Oct 23, 2026
Access Restriction Bypass in kubernetes
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
The API server in Kubernetes does not properly check admission control, which allows remote authenticated users to access additional resources via a crafted patched object.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- 10%
- Aliases
- GHSA-xx8c-m748-xr4j, GO-2022-0893
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Feb 3, 2016 · Last refreshed Oct 23, 2026