Vulnerability in Wheels
CVE-2026-111445
Wheels 4.0.0 through 4.1.2 before 4.2.0 replaces incoming scope conditions with a primary-key condition in findByKey() and exists(key=). For exists(key=), production with error information disabled returns true for an out-of-scope key instead of throwing. Applications relying on scopes for ownership or tenant authorization can therefore load and subsequently modify or delete another user's or tenant's record when the key comes from a request. The 4.2.0 fix combines key conditions with incoming scope, query-builder or where conditions in findByKey(), exists(key=), updateByKey() and deleteByKey(). Other scope-aware finders, aggregates, updateAll() and deleteAll() are not affected.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.1 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- github.com/wheels-dev/wheels/security/advisories/GHSA-2qh9-qcxq-f8qc (vendor-advisory)
Frequently asked questions
- What is CVE-2026-111445?
- CVE-2026-111445 is a high-severity vulnerability in Wheels, classified under Incorrect Resource Transfer Between Spheres. CVSS score: 8.1/10. Published 2026-10-16.
- How severe is CVE-2026-111445?
- High severity. CVSS v3 base score is 8.1 out of 10.