dbcve.org
PipeshubApplication

CVE-2025-67506

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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
PipesHub is a fully extensible workplace AI platform for enterprise search and workflow automation. Versions prior to 0.1.0-beta expose POST /api/v1/record/buffer/convert through missing authentication. The endpoint accepts a file upload and converts it to PDF via LibreOffice by uploading payload to os.path.join(tmpdir, file.filename) without normalizing the filename. An attacker can submit a crafted filename containing ../ sequences to write arbitrary files anywhere the service account has permission, enabling remote file overwrite or planting malicious code. This issue is fixed in version 0.1.0-beta.

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

PipesHub versions prior to 0.1.0-beta lack authentication on the /api/v1/record/buffer/convert endpoint, which accepts file uploads and converts them to PDF via LibreOffice. The endpoint writes uploaded files using os.path.join(tmpdir, file.filename) without normalizing the filename, allowing path traversal via ../ sequences to write arbitrary files anywhere the service account has permissions.

MitigationUpgrade to version 0.1.0-beta or implement authentication on the endpoint and add filename normalization/sanitization to prevent path traversal attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PipeshubApplication
Affected:= 0.1.0= 0.1.2= 0.1.3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checks

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

  1. Identify Pipeshub installation and version
    Run 'pip show pipeshub' or check the application's version file/documentation to determine the installed version of Pipeshub
    Affected if The installed version matches 0.1.0, 0.1.2, or 0.1.3, or falls before the patched version 0.1.0-beta
  2. Confirm the vulnerable endpoint exists
    Attempt to access or probe the /api/v1/record/buffer/convert endpoint via HTTP request (e.g., curl or similar tool) to verify it is available in the deployment
    Affected if The endpoint responds, indicating it is exposed and the application has this functionality enabled
  3. Verify authentication is not enforced on the endpoint
    Send a request to /api/v1/record/buffer/convert without providing any authentication credentials (Authorization header, session cookie, etc.) and observe if the request is processed
    Affected if The endpoint accepts and processes requests without requiring authentication credentials
  4. Check for filename sanitization in upload handling
    If source code is accessible, inspect the file upload handler for the convert endpoint and look for filename normalization (such as os.path.normpath, basename extraction, or allowlist validation) before os.path.join operations
    Affected if No filename sanitization is present and the code directly uses file.filename in os.path.join without validation

The environment is affected if Pipeshub version 0.1.0, 0.1.2, or 0.1.3 is running with the /api/v1/record/buffer/convert endpoint exposed and accessible without authentication, and the uploaded filename is not sanitized before being used in file path operations.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to version 0.1.0-beta or implement authentication on the endpoint and add filename normalization/sanitization to prevent path traversal attacks.

Recommended fix High confidence

0.1.0-beta

  1. 1. Back up your current Pipeshub installation and any custom configurations.
  2. 2. Identify your current Pipeshub version (0.1.0, 0.1.2, or 0.1.3) by checking the running service or deployment configuration.
  3. 3. Upgrade to version 0.1.0-beta which contains the security fix for the path traversal vulnerability.
  4. 4. Verify the upgrade was successful by checking the version after deployment.
  5. 5. Test that the POST /api/v1/record/buffer/convert endpoint now properly authenticates requests and sanitizes filenames.
  6. 6. Ensure LibreOffice conversion functionality continues to work correctly with legitimate file uploads.
Caveat Upgrading from stable releases to beta may introduce behavioral changes; test thoroughly in a staging environment first

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

Fix this in Pipeshub Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67506 — 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-67506 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