CVE-2026-48768
Unauthenticated file-input upload enables stored XSS via attacker-controlled content.
Is CVE-2026-48768 being exploited?
Not confirmed. CVE-2026-48768 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-48768?
CVE-2026-48768 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-48768?
Yes. A fix has been recorded for CVE-2026-48768. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-48768 affect?
CVE-2026-48768 affects TypeBot. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-48768?
Upgrade to 3.17.0+ to fix the flaw.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Anonymous, unauthenticated uploads can store attacker-controlled HTML/JS on S3/MinIO via presigned URLs, enabling stored XSS across tenants.
Immediate action required
- affected< 3.17.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.