Advisory

GHSA-vx2m-gpq4-8j5q

Details, part 2 of 2. The advisory

Details

and the same in do_OPTIONS. This keeps the dashboard working — it is served from
http://127.0.0.1:5174 and fetches 127.0.0.1:8765/8766, which is cross-origin between two
loopback ports, which I assume is exactly why the wildcard was added — while denying every
non-loopback origin.

Two optional hardening steps, if you want them:

  • Apply the existing is_loopback_origin() check to POST /control-plane/configure-goal/dry-run and POST /reward/dry-run too, so the config projection is not readable cross-origin.
  • Add a Host header check (reject a Host that is not loopback) to close DNS rebinding against clients that do not send Origin.

Scope of review

Reviewed 26/52 identified entrypoints across 758 files (360,618 LOC) of the loopx package
and dashboard; tools: semgrep 1.172.0, trufflehog 3.96.0, osv-scanner 2.4.0, plus a manual
dataflow pass. Skipped: tests/, regression/, examples/, docs/, and the benchmark
adapters under loopx/benchmark_adapters/. Coverage confidence: partial.

Other things I looked at and did not find a problem with, in case it saves you time:
self-update (curl | bash is over HTTPS to a hardcoded raw.githubusercontent.com URL; the
LOOPX_ARCHIVE_URL override requires environment control, i.e. privileges the attacker
would have to already have); project/slash-command skill installation (strict id regex plus
_assert_project_boundary() containment); the shell=True worker tick (the value is a
user-configured shell command by design, and demo_supervisor.build_visible_worker_turn_command
passes the objective through shlex.quote); outbound SSRF surfaces (content_ops/surface.py
blocks private/loopback/link-local ranges and refuses redirects). No pickle, yaml.load,
eval, or os.system anywhere in the package.

3 dependency advisories exist in dev/docs tooling only (pymdown-extensions, idna,
postcss); none are reachable from the runtime package, which declares no dependencies, so
I have not opened a bump PR.

Detected by

Aeon, an automated security review. Findings are
reproduced at HEAD and manually verified before reporting. Reported privately via GitHub PVR
because that is the intake channel your SECURITY.md designates.

Sources & licences