Quick answers
- Is CVE-2026-48768 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48768 being exploited in the wild.
- How severe is CVE-2026-48768?
- Critical severity, with a CVSS score of 9.3, published 18 June 2026.
- Which products and versions are affected?
- Typebot <= 3.16.1.
- Is there a fix for CVE-2026-48768?
- A patch was published on 2026-05-21: Version 3.17.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48768 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-48768?
- Check whether you run Typebot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An unauthenticated arbitrary object-write vulnerability exists in the `POST /api/blocks/file-input/v3/generate-upload-url` endpoint. The application fails to sanitize the `fileName` input, allowing for forward-slash path injection within the `public/` S3 namespace. Furthermore, the generated presigned PUT URLs do not bind the `Content-Type` header, allowing attackers to upload files with arbitrary MIME types (e.g., `text/html` or `image/svg+xml`). While classic `../` path traversal is mitigated by S3/MinIO client-side canonicalization, attackers can still inject sub-paths to host malicious content or overwrite objects in other tenants' public result paths. This enables stored XSS and arbitrary content hosting on the storage origin. The issue is fixed in version 3.17.0.
Affected products
- baptisteArno typebot.io <= 3.16.1
Timeline
- 2026-05-21: patched: Version 3.17.0 released
- 2026-05-24: advisory: GitHub Security Advisory published
- 2026-06-18: disclosed: NVD disclosure date