Quick answers
- Is CVE-2026-111445 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111445 being exploited in the wild.
- How severe is CVE-2026-111445?
- High severity, with a CVSS score of 8.1, published 16 October 2026.
- Which products and versions are affected?
- Wheels 4.0.0 through 4.1.2.
- Is there a fix for CVE-2026-111445?
- Yes: fixed in 4.2.0. Until then: Use findOne(where="id = #key#") or findAll(where=...) on the scope chain instead of findByKey(), or explicitly verify record ownership after loading.</anigation> <parameter name="severity">high Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111445 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111445?
- Check whether you run Wheels at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 4.2.0
Use findOne(where="id = #key#") or findAll(where=...) on the scope chain instead of findByKey(), or explicitly verify record ownership after loading.</anigation> <parameter name="severity">high
Technical details
The findByKey() and exists(key=) methods in Wheels 4.0.0–4.1.2 replace incoming scope conditions with only a primary-key lookup, ignoring chainable scopes that enforce authorization. An attacker can bypass authorization by requesting a record key outside the intended scope; findByKey() will return it and updateByKey()/deleteByKey() will modify or remove it. The fix in 4.2.0 combines key conditions with scope conditions using AND logic instead of replacement.
Affected products
- Wheels Wheels 4.0.0 through 4.1.2
Timeline
- 2026-10-12: advisory
- 2026-10-16: patched