LoopX serve-status permissive CORS policy exposes control-plane state and private Markdown files
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-108372
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 21:31 UTC · Revision 1
Source evidence
LoopX serve-status permissive CORS policy exposes control-plane state and private Markdown files
core-osv · Original sourcePublished 16 Oct 2026, 21:29 UTC
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.
osv:CVE-2026-108372
Complete source record
{
"id": "3245a1db24050f83f889f865081d2ed08e16ed9bbc89159d7e641e6e7a0bb7c0",
"url": "https://osv.dev/vulnerability/CVE-2026-108372",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "LoopX serve-status permissive CORS policy exposes control-plane state and private Markdown files",
"summary": "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.",
"evidence": "osv:CVE-2026-108372",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-108372",
"aliases": [
"CVE-2026-108372",
"GHSA-vx2m-gpq4-8j5q"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/loopx-project/loopx",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "80877982216577174e3e7c7cca9804c5a3a3148b"
},
{
"fixed": "838720fba42bd22f71b5bb763ec406f7bdf4c940"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0.0.1"
},
{
"fixed": "0.4.5"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "838720fba42bd22f71b5bb763ec406f7bdf4c940"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "80877982216577174e3e7c7cca9804c5a3a3148b"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v0.4.5"
}
]
}
}
],
"versions": [
"v0.4.4",
"v0.4.3",
"v0.4.1",
"v0.4.0",
"v0.3.0",
"v0.2.13",
"v0.2.12",
"v0.2.11",
"v0.2.10",
"v0.2.9",
"v0.2.8",
"v0.2.5",
"v0.2.4",
"v0.2.3",
"v0.2.2",
"v0.2.1",
"v0.2.0",
"v0.1.16",
"v0.1.15",
"v0.1.14",
"v0.1.13",
"v0.1.12",
"v0.1.11",
"v0.1.10",
"v0.1.9",
"v0.1.8",
"v0.1.7",
"v0.1.6",
"v0.1.5",
"v0.1.4",
"v0.1.3"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-108372.json"
}
}
],
"modified": "2026-10-28T02:30:39.752917711Z",
"provider": "osv",
"references": [
"https://github.com/loopx-project/loopx/releases/tag/v0.4.5",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/108xxx/CVE-2026-108372.json",
"https://github.com/loopx-project/loopx/security/advisories/GHSA-vx2m-gpq4-8j5q",
"https://nvd.nist.gov/vuln/detail/CVE-2026-108372",
"https://github.com/loopx-project/loopx/commit/838720fba42bd22f71b5bb763ec406f7bdf4c940",
"https://github.com/loopx-project/loopx/pull/3137"
],
"provider_metadata": {
"cwe_ids": [
"CWE-346",
"CWE-942"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/108xxx/CVE-2026-108372.json"
}
},
"related_cves": [
{
"value": "CVE-2026-108372",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 507307,
"published_at": "2026-10-16T21:29:13.757+00:00"
}