Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Affected: loopx versions from 0.0.1 before 0.4.5 (fixed in 0.4.5). The loopx serve-status server sends a wildcard CORS header on all responses, including unauthenticated read routes, so any website visited while it runs can read status data and the contents of Markdown files in registered goal repos without user interaction. The source gives few details on whether the attack needs anything beyond the server running and a visited page. Upgrade to loopx 0.4.5 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.1 | High | 4.0 | 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 | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0030, the 23rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:08 UTC First seen by agentprime
- 31 Oct 2026, 14:08 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-vx2m-gpq4-8j5q
- OSV: GHSA-vx2m-gpq4-8j5q
- github.com/huangruiteng/loopx/security/advisories/GHSA-vx2m-gpq4-8j5q
- github.com/loopx-project/loopx/security/advisories/GHSA-vx2m-gpq4-8j5q
- nvd.nist.gov/vuln/detail/CVE-2026-108372
- github.com/loopx-project/loopx/pull/3137
- github.com/loopx-project/loopx/commit/838720fba42bd22f71b5bb763ec406f7bdf4c940
- github.com/huangruiteng/loopx
- github.com/loopx-project/loopx/releases/tag/v0.4.5