Unauthenticated arbitrary S3 object write in TypeBot generate-upload-url
CVE-2026-48768 affects TypeBot versions 3.16.1 and earlier. The POST /api/blocks/file-input/v3/generate-upload-url endpoint is unauthenticated and uses unsanitized fileName input when constructing object keys under the public/ storage path, while also issuing presigned PUT URLs that do not bind Content-Type. An anonymous visitor to a published bot that includes a file input can therefore obtain a valid upload URL and write attacker-controlled content such as HTML, SVG, or JavaScript to attacker-chosen subpaths, including publicly served result paths belonging to other tenants. The issue is not based on ../ traversal, which is blocked by S3/MinIO canonicalization and signature mismatch, but on exploitable forward-slash path injection in the supplied fileName.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.