Gorse EUVD-2026-40158

Two concrete conditions, both satisfied by default: (1) the Gorse HTTP API must be network-reachable by the attacker, and (2) admin_api_key must be empty - which is the shipped default configuration. When both hold, the /api/dump and /api/restore endpoints accept unauthenticated requests. What LIMITS exploitation: if an operator has set a non-empty admin_api_key, the endpoints enforce authentication and the bypass does not apply; likewise, instances whose API is bound to localhost or firewalled off from untrusted networks are not remotely exploitable. No user interaction, no prior authentication, and no non-default feature toggle are required beyond the default empty key.

All available signals point to genuine high priority on exposed instances. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes network-reachable, low-complexity, no-privilege, no-interaction exploitation, and the high vulnerable-system C/I/A (VC:H/VI:H/VA:H) reflects both full data theft and destructive overwrite from a single request - consistent with the description. The mitigating reality is exposure scope: exploitation requires network reachability to the Gorse API and the default empty admin_api_key, so hardened deployments that set a key or firewall the API are not affected. No EPSS score, KEV listing, or POC was provided, so widespread automated exploitation is not evidenced; this is best treated as a high-impact, easily-weaponizable flaw whose real-world exposure depends on how many Gorse instances are reachable from untrusted networks with default config. No data conflicts were observed between the CVSS vector and the description.

An attacker scans for internet-exposed Gorse instances and sends an unauthenticated GET to /api/dump, receiving the entire dataset - user records, items, and feedback containing PII - in a single response. The same actor can then POST to /api/restore to overwrite the production dataset with poisoned or empty data, corrupting recommendations or destroying the database. No POC was provided, but the low attack complexity (AC:L) and absence of authentication or user interaction make exploitation straightforward to script.