GPU VulnDB

Database/Container, Kubernetes & orchestration

HAProxy Kubernetes Ingress Controller: config snippets leak the ingress token secret

CVSS 6.4CVE-2025-59303Container, Kubernetes & orchestrationcurated

Impact

Where the config-snippets feature flag is enabled, a namespace tenant holding create/update on Ingress objects can submit a snippet whose response returns the controller's ingress token secret. That token is cluster-level ingress credential material, so the blast radius crosses the namespace boundary that a multi-tenant GPU cluster relies on to separate customers. The leak requires only the ordinary Ingress write permission a tenant is usually given, which is why this scores as a privilege boundary failure rather than a configuration mistake.

Who can reach it

Any authenticated Kubernetes user or service account with create/update on Ingress resources in a cluster where config-snippets is enabled.

What to do

Upgrade the community controller to 3.1.13 or later; HAProxy Enterprise fixes are 3.0.16-ee1, 1.11.13-ee1 and 1.9.15-ee1. Interim mitigation is to disable the config-snippets feature flag. Either path is a controller deployment rollout, not a node operation; rotate the ingress token afterwards if snippets were ever enabled with untrusted tenants.

References

Related entries

All Container, Kubernetes & orchestration entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.