dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-58061

MEDIUM · 5.5 CVSS v3.1 Published 2025-08-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
OpenEBS Local PV RawFile allows dynamic deployment of Stateful Persistent Node-Local Volumes & Filesystems for Kubernetes. Prior to version 0.10.0, persistent volume data is world readable and that would allow non-privileged users to access sensitive data such as databases of k8s workload. The rawfile-localpv storage class creates persistent volume data under /var/csi/rawfile/ on Kubernetes hosts by default. However, the directory and data in it are world-readable. It allows non-privileged users to access the whole persistent volume data, and those can include sensitive information such as a whole database if the Kubernetes tenants are running MySQL or PostgreSQL in a container so it could lead to a database breach. This issue has been patched in version 0.10.0.

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 · high confidence

OpenEBS Local PV RawFile storage class creates persistent volume data under /var/csi/rawfile/ on Kubernetes hosts. Prior to version 0.10.0, this directory and all contained data are world-readable (mode 0777 or equivalent), allowing any non-privileged user on the host to read sensitive data including entire database files from Kubernetes workloads running MySQL or PostgreSQL.

MitigationUpgrade OpenEBS Local PV RawFile to version 0.10.0 or later, which contains the security fix for proper permission handling. For existing deployments, audit and restrict permissions on /var/csi/rawfile/ to the csi-node-agent user/group.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenEBS Local PV RawFile installation
    Run 'kubectl get sc' to list storage classes and look for any storage class with 'rawfile' in the name or 'Local PV' type. Also check 'kubectl get pods -n openebs' to see if OpenEBS components are running.
    Affected if A storage class named 'rawfile' or 'localpv-rawfile' exists and is set as default or in use.
  2. Check OpenEBS version
    Run 'kubectl get pods -n openebs -o jsonpath="{.items[*].spec.containers[*].image}"' to get container images, or check the openebs-operator deployment. Compare the version to 0.10.0.
    Affected if The installed OpenEBS version is below 0.10.0.
  3. Verify /var/csi/rawfile/ directory exists on nodes
    SSH to each Kubernetes node and run 'ls -la /var/csi/' to check if the rawfile directory exists. Run 'stat /var/csi/rawfile/' on nodes where the directory is present.
    Affected if The /var/csi/rawfile/ directory exists on any node.
  4. Check permissions on rawfile directory
    On nodes with /var/csi/rawfile/, run 'ls -la /var/csi/rawfile/' and check the directory mode. Also check 'getfacl /var/csi/rawfile/' if available.
    Affected if The directory shows mode 0777 or equivalent (rwxrwxrwx) in ls output, indicating world-readable permissions.
  5. Check for sensitive workload data
    Run 'ls -la /var/csi/rawfile/' to list any subdirectories (these are PVs). Check if any subdirectory contains MySQL or PostgreSQL data files (look for ibdata1, mysql/, pg_data/, or similar).
    Affected if Persistent volumes containing database files exist in the world-readable directory.

You are affected if OpenEBS Local PV RawFile with version below 0.10.0 is installed and the /var/csi/rawfile/ directory exists with 0777 permissions, exposing Kubernetes persistent volumes to any local user.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade OpenEBS Local PV RawFile to version 0.10.0 or later, which contains the security fix for proper permission handling. For existing deployments, audit and restrict permissions on /var/csi/rawfile/ to the csi-node-agent user/group.

Recommended fix High confidence

0.10.0

  1. Identify the current OpenEBS installation method (helm or kubectl)
  2. For helm-based installations: run 'helm repo update' and then 'helm upgrade openebs openebs/openebs -n openebs' to upgrade to the version containing 0.10.0
  3. For kubectl-based installations: apply the updated operator YAML from the OpenEBS 0.10.0 release
  4. Verify the rawfile-localpv storage class is using version 0.10.0 or later by running 'kubectl get sc' and checking the version annotation
  5. Ensure new PVCs created after the upgrade have correct permissions (not world-readable)
  6. For existing volumes, manually review and correct permissions on /var/csi/rawfile/ directories if needed
Caveat Review OpenEBS 0.10.0 release notes for any breaking changes or migration requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58061 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58061 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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