CVE-2025-1767

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.

Published: 2025-03-13 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-1767 is rated Moderate Risk (43.9/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.27%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-1767

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-01 0.23% 0.27% +0.04%
2 2026-05-19 0.25% 0.23% -0.02%
3 2026-04-21 — 0.25% —

Full EPSS history (11 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-1767

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.2 5.2 [email protected]

Weakness enumeration for CVE-2025-1767

GitHub Security Advisory for CVE-2025-1767

GHSA-3wgm-2gw2-vh5m · Severity: medium · Ecosystem: go — Kubernetes GitRepo Volume Inadvertent Local Repository Access

OS Trackers for CVE-2025-1767

vendor priority summary link
debian not yet assigned CVE-2025-1767 not yet assigned priority: Debian including 1 source packages (kubernetes), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-1767
redhat medium — https://access.redhat.com/security/cve/CVE-2025-1767
suse medium CVE-2025-1767 severity moderate: SUSE including 123 source package names (cloud-init-25.1.3-slfo.1.1_1.1, cloud-init-config-suse-25.1.3-slfo.1.1_1.1, …), 323 product×package rows across 26 product lines (Image SLE-Micro, Image SLE-Micro-Azure, … (26 product lines)): Known Not Affected 265, Fixed 58. https://www.suse.com/security/cve/CVE-2025-1767/
ubuntu medium CVE-2025-1767 medium priority: Ubuntu including 1 source packages (kubernetes), 5 status rows across 5 suites (focal, jammy, noble, oracular, upstream): not-affected 4, needs-triage 1. https://ubuntu.com/security/CVE-2025-1767

Affected software / configurations for CVE-2025-1767

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-1767

cvelogic Threat Intelligence