CLEANSTART-2026-BQ17139: Kubernetes kube-controller-manager in versions v1

Q: What level of access and interaction does exploitation require?

The supplied vector indicates network access, high attack complexity, and low privileges are required. No user interaction is required.

Q: What is the potential impact if exploitation succeeds?

The vector indicates high confidentiality impact, with no integrity or availability impact. It also indicates a scope change.

Q: Can this record be used to identify exact affected and fixed releases?

No. The supplied data refers to Kubernetes kube-controller-manager versions v1 but does not provide specific affected release ranges or a fixed version.

Q: Is a workaround available if patching cannot happen immediately?

No workaround or mitigation is provided in the supplied data.

Published Nov 5, 2026

Updated

Security vulnerability affects the nfs-subdir-external-provisioner package. The Kubernetes kube-controller-manager in versions v1.

Affected Software

1 affected componentFixes available

cleanstart/nfs-subdir-external-provisioner<4.0.2-r4

4.0.2-r4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade cleanstart/nfs-subdir-external-provisioner to a version that resolves this vulnerability.
Fixed in 4.0.2-r4

Event History

Nov 5, 2026

Advisory Published

via OSV·08:10 AM

Data Sourced

via OSV·08:10 AM

DescriptionSeverityAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

CVE-2020-8555

Frequently Asked Questions

What level of access and interaction does exploitation require?

The supplied vector indicates network access, high attack complexity, and low privileges are required. No user interaction is required.

What is the potential impact if exploitation succeeds?

The vector indicates high confidentiality impact, with no integrity or availability impact. It also indicates a scope change.

Can this record be used to identify exact affected and fixed releases?

No. The supplied data refers to Kubernetes kube-controller-manager versions v1 but does not provide specific affected release ranges or a fixed version.

Is a workaround available if patching cannot happen immediately?

No workaround or mitigation is provided in the supplied data.

CLEANSTART-2026-BQ17139: Kubernetes kube-controller-manager in versions v1

Affected Software

Remediation

Event History

Child vulnerabilities

Frequently Asked Questions

What level of access and interaction does exploitation require?

What is the potential impact if exploitation succeeds?

Can this record be used to identify exact affected and fixed releases?

Is a workaround available if patching cannot happen immediately?

Company

Resources

Contact

Frequently Asked Questions

What level of access and interaction does exploitation require?

What is the potential impact if exploitation succeeds?

Can this record be used to identify exact affected and fixed releases?

Is a workaround available if patching cannot happen immediately?