# CVE-2026-108372: LoopX serve-status permissive CORS policy exposes control-plane state and private Markdown files

> A permissive CORS policy in LoopX allows remote attackers to read control-plane state and private files via cross-origin requests from a victim's browser.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 16 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-vx2m-gpq4-8j5q

## What is CVE-2026-108372?

CVE-2026-108372 is a high-severity vulnerability in huangruiteng loopx, published on 16 Oct 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

Open and provider-neutral, LoopX is a lightweight state kernel and local-first control plane for loop engineering. From version 0.0.1 until 0.4.5, `loopx serve-status` in `loopx/status_server.py` uses `StatusRequestHandler._send_json()` and `do_OPTIONS()` to send `Access-Control-Allow-Origin: *` for unauthenticated responses on predictable loopback ports. A remote attacker can cause an operator who visits attacker-controlled web content to issue cross-origin requests to `GET /status.json`, `GET /review-material?goal_id=...&path=...`, `GET /`, and `POST /control-plane/configure-goal/dry-run`, exposing control-plane state, goal and run information, local absolute paths, private Markdown files below registered goal roots, and dry-run configuration projections. The affected routes do not provide cross-origin writes or arbitrary-file access. This issue is fixed in version 0.4.5.

Weakness: CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains), CWE-346 (Origin Validation Error)

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

2 open source packages ship an affected version, including loopx.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `loopx` | PyPI | From 0.0.1 | 0.4.5 |
| `loopx` | PyPI | From 0.0.1 | 0.4.5 |

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

Upgrade loopx to 0.4.5 or later.

## Is CVE-2026-108372 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108372 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108372 is a high-severity vulnerability in huangruiteng loopx, published on 16 Oct 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108372 exists.

Affected packages and fixed versions:
- loopx (PyPI): affected from 0.0.1; fixed in 0.4.5
- loopx (PyPI): affected from 0.0.1; fixed in 0.4.5

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-108372/ (Markdown: https://insights.sbomify.com/CVE-2026-108372/index.md)
```

## Sources

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

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