Skip to content
Cloud

CVE-2026-48763

8.2
High
EPSS 0.39%Patch availableAug 12, 2026

Unauthenticated generation of S3 presigned PUT URLs enabling cross-tenant uploads.

common questions

Is CVE-2026-48763 being exploited?

Not confirmed. CVE-2026-48763 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.39% probability of exploitation in the next 30 days.

How severe is CVE-2026-48763?

CVE-2026-48763 is rated High with a CVSS score of 8.2. 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-48763?

Yes. A fix has been recorded for CVE-2026-48763. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-48763 affect?

CVE-2026-48763 affects TypeBot <3.17.0, API: GET /api/v1/typebots/{typebotId}/blocks/{blockId}/storage/upload-url, Shared S3 bucket (presigned PUT URLs). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-48763?

Upgrade to TypeBot 3.17.0 immediately; or disable endpoint and restrict S3 key access.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
TypeBot <3.17.0API: GET /api/v1/typebots/{typebotId}/blocks/{blockId}/storage/upload-urlShared S3 bucket (presigned PUT URLs)
impact

Unauthenticated attacker can obtain presigned S3 PUT URLs for arbitrary keys, allowing cross-tenant file upload/overwrite and data injection.

action required

Immediate action required

affected versions
baptisteArno typebot.io
  • 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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free