VULNpocalypse

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

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-11 15:49 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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.

Description quoted from the CVE record (assigned by GitHub_M, published 2026-10-16).

Weakness: CWE-346: Origin Validation Error; CWE-942: Permissive Cross-domain Policy with Untrusted Domains

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and a user must take an action. Impact: confidentiality high, integrity none, availability none. 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

CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: yes. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 2 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 7 references on Exploit Observer

Live scores

EPSS
0.003
low predicted chance of attack
VEDAS
0.986
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Nuclei

Who is affected

ProductAffectedNot affected
huangruiteng loopxversion >= 0.0.1, < 0.4.5Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Nuclei template (active check)

LoopX - Missing Authentication Status Server Exposure

LoopX from version 0.0.1 until 0.4.5 runs `loopx serve-status` with a status server that sends `Access-Control-Allow-Origin: *` and serves unauthenticated read endpoints on predictable loopback ports. An unauthenticated caller who can reach the listener can request `GET /status.json` to disclose control-plane state, goal and run information, and local absolute paths such as the registry and runtime root. This issue is fixed in version 0.4.5.

Name and description quoted from the template, written by VEDAS.

The template sends 1 request (GET /status.json); it decides using dsl matchers. Severity in the template: high. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash
nuclei -u https://your-host -t CVE-2026-108372.yaml
Show the template (38 lines)
yaml
id: CVE-2026-108372

info:
  name: "LoopX - Missing Authentication Status Server Exposure"
  author: vedas-arpsyndicate
  severity: high
  description: |
    LoopX from version 0.0.1 until 0.4.5 runs `loopx serve-status` with a status server that sends
    `Access-Control-Allow-Origin: *` and serves unauthenticated read endpoints on predictable loopback
    ports. An unauthenticated caller who can reach the listener can request `GET /status.json` to disclose
    control-plane state, goal and run information, and local absolute paths such as the registry and runtime
    root. This issue is fixed in version 0.4.5.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-108372&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=loopx&match=exact
  classification:
    cvss-metrics: 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
    cvss-score: 8.2
    cve-id: CVE-2026-108372
    cwe-id: CWE-346
  metadata:
    verified: false
  tags: cve,cve2026,loopx,cors,auth-bypass,exposure
http:
  - raw:
      - |
        GET /status.json HTTP/1.1
        Host: {{Hostname}}
        Accept: application/json

    matchers-condition: and
    matchers:
      - type: dsl
        dsl:
          - 'status_code == 200'
          - 'contains(tolower(header), "access-control-allow-origin: *")'
          - 'contains_all(body, "\"goals\"", "\"registry\"", "\"runtime_root\"")'
        condition: and

CVE-2026-108372.yaml on GitHub

References

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners

Feasible SecurityAskealGoTrust