Joro: Unauthenticated Cross-Origin Plugin Upload Leads to RCE

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

EPSS

• CVE-2026-53649: 0.33% estimated exploitation activity in the next 30 days; percentile 26.18 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Unauthenticated Cross-Origin Plugin Upload Leads to RCE (Joro ≤ v1.1.0) Severity: Critical CVSS v3.1: 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) Affected versions: Joro ≤ v1.1.0, proxy mode (default), Linux/macOS Reporter: cstover Date: 2026-05-27 --- Summary Joro's default proxy mode (in versions <= 1.1.0) exposes a local API on 127.0.0.1:9090 that performs no authentication and applies a wildcard CORS policy. Because plugin uploads use the CORS-safelisted multipart/form-data content type, cross-origin JavaScript on any page the operator visits can reach privileged endpoints - including uploading a native plugin and triggering a restart - directly through the operator's browser, with no preflight or credentials. Since plugins execute on load, this yields unauthenticated remote code execution as the operator's user from a single page visit. --- Root Cause Three weaknesses combined into the exploit chain. 1. No authentication in proxy mode. internal/api/server.go applied AuthMiddleware…

Published by the source

8 Jul 2026, 20:27 UTC

Last modified by the source

8 Jul 2026, 20:27 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xqhv-chqm-fhcc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-53649

Advisory: Joro: Unauthenticated Cross-Origin Plugin Upload Leads to RCE
IDs: CVE-2026-53649, GHSA-xqhv-chqm-fhcc
Record: https://patchnext.com/advisories/cve-2026-53649 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/BishopFox/joro 0.0.0-20260601151442-5c0ca35db828. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/BishopFox/joro: affected < 0.0.0-20260601151442-5c0ca35db828; fixed in 0.0.0-20260601151442-5c0ca35db828

## Suggested inspection (read-only)
- Go github.com/BishopFox/joro: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/BishopFox/joro.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xqhv-chqm-fhcc (GitHub-reviewed advisory GHSA-xqhv-chqm-fhcc lists affected ranges: Go github.com/BishopFox/joro >=0 <0.0.0-20260601151442-5c0ca35db828)

Commands are suggestions: review each one before running it.