CVE-2025-1767: [kubernetes] CVE-2025-1767: Gitpo Volume Inadvertent Local pository Access
A security vulnerability was discovered in Kubernetes that could allow a user with create pod permission to exploit gitRepo volumes to access local git repositories belonging to other pods on the same node. This CVE only affects Kubernetes clusters that utilize the in-tree gitRepo volume to clone git repositories from other pods within the same node. Since the in-tree gitRepo volume feature has been deprecated and will not receive security updates upstream, any cluster still using this feature remains vulnerable.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-1767?
CVE-2025-1767 is considered to have a moderate severity due to its impact on Kubernetes clusters utilizing the deprecated in-tree gitRepo volume.
How do I fix CVE-2025-1767?
To fix CVE-2025-1767, you should migrate away from the in-tree gitRepo volume feature to a supported volume type that is actively maintained.
What versions of Kubernetes are affected by CVE-2025-1767?
CVE-2025-1767 affects all Kubernetes versions that are using the in-tree gitRepo volume feature.
What are the implications of CVE-2025-1767 for Kubernetes security?
The implications of CVE-2025-1767 include potential exposure to security vulnerabilities since the feature will not receive updates.
Is CVE-2025-1767 related to any deprecated features in Kubernetes?
Yes, CVE-2025-1767 is specifically related to the in-tree gitRepo volume feature, which has been deprecated in Kubernetes.