Quick answers
- Is CVE-2026-110098 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110098 being exploited in the wild.
- How severe is CVE-2026-110098?
- Medium severity, with a CVSS score of 5.4, published 13 October 2026.
- Which products and versions are affected?
- Jorani before 1.0.4.
- Is there a fix for CVE-2026-110098?
- Yes: fixed in 1.0.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-110098 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-110098?
- Check whether you run Jorani 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: 1.0.4
Technical details
The vulnerability is an insecure direct object reference (IDOR) in the Leaves and Extra controllers where authorization checks rely only on operation names rather than validating ownership of the target request. Authenticated attackers can supply numeric request IDs to edit(), delete(), and history() methods to access and manipulate colleagues' records without proper access control checks.
Affected products
- Jorani Jorani before 1.0.4
Timeline
- 2026-10-13: disclosed