Skip to main content
Vulnerability Database/CVE-2026-100625

CVE-2026-100625: Capgo TUS Upload Proxy Privilege Escalation

CVE-2026-100625 is a privilege escalation vulnerability in Capgo's native build TUS upload proxy that allows attackers to corrupt build artifacts across different jobs. This article covers technical details, exploitation risks, and available mitigations.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-100625 Overview

Capgo (capgo.app) contains an authorization bypass in its native build TUS upload proxy at supabase/functions/_backend/public/build/upload.ts. The proxy authorizes a caller against a single build job identified by builder_job_id and validates that job's stored upload_path. However, it then forwards a user-controlled TUS resource suffix from /build/upload/:jobId/* to the builder service while injecting Capgo's privileged builder API key. Because the forwarded suffix is never bound to the authorized job's upload_path or upload_session_key, a caller holding a valid all or write API key with app.build_native permission for one application can corrupt another job's build artifacts. All versions are affected and no patch was available at the time of advisory publication.

Critical Impact

An authenticated attacker with a low-privileged Capgo API key can overwrite TUS upload resources belonging to unrelated build jobs, corrupting other tenants' native build artifacts.

Affected Products

  • Capgo (capgo.app) native build upload proxy
  • supabase/functions/_backend/public/build/upload.ts endpoint
  • All versions at time of advisory publication

Discovery Timeline

  • 2026-09-26 - CVE-2026-100625 published to NVD
  • 2026-09-30 - Last updated in NVD database

Technical Details for CVE-2026-100625

Vulnerability Analysis

The flaw is an authorization bypass [CWE-441] in the Capgo native build upload proxy. The proxy accepts requests at /build/upload/:jobId/*, where :jobId identifies a build job the caller is authorized to write to. Server-side logic queries that job's record, confirms the API key has app.build_native permission, and reads the stored upload_path and upload_session_key for job A.

The wildcard suffix is then forwarded to the backend TUS builder service with Capgo's privileged builder API key injected into the request. The forwarded suffix is treated as an opaque TUS resource identifier and is never cross-checked against the upload_path or upload_session_key associated with the authorized job. An attacker who knows or guesses the TUS resource suffix for job B can submit it through their own authorized proxy path for job A.

The builder service receives the request bearing the trusted internal API key and services the write against job B's TUS resource. The result is cross-tenant artifact corruption: the attacker can overwrite the native build output of another application without ever holding credentials for it.

Root Cause

The root cause is a confused-deputy pattern. The proxy enforces authorization on :jobId but trusts the caller-supplied wildcard path when constructing the upstream request. Binding of the authorized job to the forwarded TUS resource is missing, so the privileged builder API key is used to perform an action the caller was never authorized to perform.

Attack Vector

Exploitation requires a valid Capgo API key of type all or write with the app.build_native scope for at least one application the attacker controls. The attacker initiates a legitimate build on their own application to obtain a working jobId and authorization context. They then issue a TUS upload request to /build/upload/:ownJobId/<victimTusSuffix>, substituting a known or disclosed TUS resource suffix belonging to a victim build job. The proxy authorizes the request against the attacker's job and forwards the write to the victim's TUS resource with Capgo's privileged key attached.

See the GitHub Security Advisory GHSA-r45q-x4gr-3mvv and the VulnCheck Advisory on Authorization Bypass for additional technical detail.

Detection Methods for CVE-2026-100625

Indicators of Compromise

  • Requests to /build/upload/:jobId/* where the wildcard suffix does not match the upload_path stored for :jobId.
  • TUS PATCH or HEAD requests against builder resources that originate from an API key not associated with the owning application.
  • Unexpected changes in build artifact size, hash, or signature for jobs whose owner did not initiate an upload.

Detection Strategies

  • Log and compare the :jobId authorization context against the forwarded TUS resource suffix at the proxy layer, alerting on any mismatch.
  • Correlate builder-service upload events with the Capgo API key that initiated the proxy call and flag writes to resources outside that key's application scope.
  • Review historical proxy access logs for suffix values that reference jobs other than the one authorized in the path.

Monitoring Recommendations

  • Instrument supabase/functions/_backend/public/build/upload.ts to emit structured events tying builder_job_id, API key ID, application ID, and forwarded TUS suffix.
  • Monitor the builder service for TUS writes performed with the privileged builder API key where the originating caller identity cannot be reconciled to the resource owner.
  • Alert on anomalous build artifact modifications occurring outside of a user-initiated build session.

How to Mitigate CVE-2026-100625

Immediate Actions Required

  • Restrict issuance of all and write API keys with app.build_native permission to trusted principals only.
  • Rotate any Capgo API keys that may have been exposed to untrusted parties.
  • Audit recent native build artifacts for unexpected modifications or integrity failures and rebuild affected applications from source.

Patch Information

No patch was available at the time of advisory publication. Monitor the GitHub Security Advisory GHSA-r45q-x4gr-3mvv for an official fix. The remediation requires the proxy to bind the forwarded TUS resource suffix to the upload_path or upload_session_key of the authorized builder_job_id before injecting the privileged builder API key.

Workarounds

  • Disable or gate the native build upload proxy route for self-hosted Capgo deployments until a fix is available.
  • Enforce proxy-side validation that the TUS resource suffix matches the upload_path recorded for the authorized job, rejecting mismatches with HTTP 403.
  • Scope builder API key usage so that each forwarded request can only act on resources owned by the authenticated application.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.