CVE-2025-62878
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA malicious user can manipulate the parameters.pathPattern to create PersistentVolumes in arbitrary locations on the host node, potentially overwriting sensitive files or gaining access to unintended directories.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA path traversal vulnerability exists in PersistentVolume creation where a malicious user can manipulate the parameters.pathPattern to create PersistentVolumes at arbitrary locations on the host node, enabling file overwrite and unauthorized directory access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify PersistentVolume creation permissionQuery the RBAC or authorization system to enumerate which users or service accounts have permissions to create PersistentVolumes ( verbs: create on resource: persistentvolumes)Affected if Users or service accounts without proper restrictions can create PersistentVolumes
-
Inspect PersistentVolume spec for pathPattern fieldReview the PersistentVolume specification schema or API definition to confirm whether the pathPattern parameter field is accepted and optionalAffected if The pathPattern field is accepted in PersistentVolume specs without mandatory sanitization validation
-
Check for pathPattern values in existing PersistentVolumesList all existing PersistentVolumes (kubectl get pv -o yaml or equivalent API call) and inspect any that specify a pathPattern parameter, looking for patterns like '../' or absolute paths outside expected directoriesAffected if Any PersistentVolume contains pathPattern values pointing to locations outside the designated storage directory
-
Verify admission control for pathPattern validationReview the admission webhook or validation policies applied during PersistentVolume creation to confirm whether pathPattern input validation or allowlisting is implementedAffected if No admission controller or validation policy specifically sanitizes or validates the pathPattern parameter before PV creation
-
Test pathPattern input with traversal sequencesIf authorized to test, attempt to create a PersistentVolume with a pathPattern containing '../' sequences or absolute paths to locations outside the intended storage rootAffected if The system accepts pathPattern values containing directory traversal sequences without rejection
A user is affected if they have permission to create PersistentVolumes and the pathPattern field is accepted without strict validation or allowlisting, allowing arbitrary path specification on the host filesystem.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation and path sanitization for the pathPattern parameter, restricting PV creation to explicitly allowed directories and implementing allowlist-based path validation.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62878 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-62878 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data