# CVE-2026-53649: Joro: Unauthenticated Cross-Origin Plugin Upload Leads to RCE

> Unauthenticated cross-origin plugin upload in Joro allows remote code execution via a single page visit due to missing authentication and wildcard CORS.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-xqhv-chqm-fhcc, GO-2026-5947

## What is CVE-2026-53649?

CVE-2026-53649 is a critical vulnerability in BishopFox joro, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Joro is a web exploitation framework. Prior to version 1.1.1, Joro's default proxy mode 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. This issue has been patched in version 1.1.1.

Weakness: CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains), CWE-352 (Cross-Site Request Forgery), CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-53649?

3 open source packages ship an affected version, including github.com/BishopFox/joro.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/BishopFox/joro` | Go | All versions | 0.0.0-20260601151442-5c0ca35db828 |
| `github.com/BishopFox/joro` | Go | All versions | 0.0.0-20260601151442-5c0ca35db828 |
| `github.com/BishopFox/joro` | Go | All versions | 0.0.0-20260601151442-5c0ca35db828 |

## How do I fix CVE-2026-53649?

Upgrade github.com/BishopFox/joro to 0.0.0-20260601151442-5c0ca35db828 or later.

## Is CVE-2026-53649 being exploited?

There is no known exploitation of CVE-2026-53649 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53649 and fix it if it is affected.

What it is: CVE-2026-53649 is a critical vulnerability in BishopFox joro, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-53649 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/BishopFox/joro (Go): affected all versions; fixed in 0.0.0-20260601151442-5c0ca35db828
- github.com/BishopFox/joro (Go): affected all versions; fixed in 0.0.0-20260601151442-5c0ca35db828
- github.com/BishopFox/joro (Go): affected all versions; fixed in 0.0.0-20260601151442-5c0ca35db828

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53649/ (Markdown: https://insights.sbomify.com/CVE-2026-53649/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53649
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53649
- OSV: https://osv.dev/vulnerability/CVE-2026-53649

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53649/
Summaries are generated and may contain mistakes; the official description above is the record.