dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-48768

CRITICAL · 9.3 CVSS v3.1 Published 2026-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
TypeBot is a chatbot builder tool. In versions 3.16.1 and earlier, POST /api/blocks/file-input/v3/generate-upload-url is unauthenticated and uses unsanitized fileName input to construct public/ S3 object keys, while issuing presigned PUT URLs that do not bind Content-Type. As a result, any anonymous visitor to a published bot with a file input can upload attacker-controlled HTML, SVG, or JS to attacker-chosen subpaths, including other tenants’ publicly served result paths, enabling arbitrary content hosting and potential stored XSS on the storage origin. ../ traversal is blocked by S3/MinIO canonicalization (signature mismatch), but forward-slash path injection is exploitable. This issue has been fixed in version 3.17.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

TypeBot versions 3.16.1 and earlier have an unauthenticated file upload vulnerability in the POST /api/blocks/file-input/v3/generate-upload-url endpoint. The fileName parameter is not sanitized when constructing S3 object keys, and presigned PUT URLs do not bind Content-Type, allowing anonymous visitors to upload attacker-controlled HTML, SVG, or JavaScript to arbitrary subpaths including other tenants' publicly served paths, enabling stored XSS.

MitigationUpgrade to TypeBot version 3.17.0 or later, which implements proper input sanitization for fileName and binds Content-Type to presigned URLs.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/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 TypeBot installation and version
    Check your running TypeBot instance version by querying the /api/health endpoint, checking the Docker image tag, or reviewing your deployment configuration (docker-compose.yml, Helm values, or package.json if self-hosted). Compare the version number to 3.16.1 or earlier.
    Affected if The installed TypeBot version is 3.16.1 or any earlier version.
  2. Verify the vulnerable endpoint is exposed
    Send a POST request to /api/blocks/file-input/v3/generate-upload-url without authentication. Use a tool like curl: curl -X POST https://your-typebot-domain/api/blocks/file-input/v3/generate-upload-url -H 'Content-Type: application/json' -d '{"fileName":"test.png"}'.
    Affected if The endpoint responds with a 200 OK and returns a presigned S3 PUT URL without requiring authentication.
  3. Confirm S3 storage is configured
    Review your TypeBot environment configuration (Docker environment variables, .env file) for S3-compatible storage settings: S3_BUCKET, S3_ACCESS_KEY_ID, S3_SECRET_ACCESS_KEY, S3_ENDPOINT, and S3_REGION. Check if any S3-compatible provider (AWS S3, MinIO, DigitalOcean Spaces) is configured.
    Affected if S3 storage is configured and the file upload feature uses S3 for storing uploaded files.
  4. Check if file-input blocks are used in flows
    Access the TypeBot builder interface and review your bot flows for any file-input blocks, or query the TypeBot database (if accessible) for blocks where type equals 'file-input' in the blocks collection.
    Affected if Any published bot flow contains file-input blocks that allow visitors to upload files.

You are affected if TypeBot version is 3.16.1 or earlier, the /api/blocks/file-input/v3/generate-upload-url endpoint is exposed without authentication, S3 storage is configured, and file-input blocks are enabled in any published bot flow.

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 to TypeBot version 3.17.0 or later, which implements proper input sanitization for fileName and binds Content-Type to presigned URLs.

Recommended fix High confidence

3.17.0

  1. Back up your current TypeBot installation and database before upgrading
  2. Upgrade TypeBot to version 3.17.0 using your deployment method (Docker, npm, or manual update)
  3. Verify the upgrade was successful by checking the installed version

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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