Quick answers
- Is CVE-2026-48249 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48249 being exploited in the wild.
- How severe is CVE-2026-48249?
- Medium severity, with a CVSS score of 5.9, published 21 May 2026.
- Which products and versions are affected?
- Open ISES Tickets < 3.44.2.
- Is there a fix for CVE-2026-48249?
- A patch was published on 2026-04-01: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48249 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-48249?
- Check whether you run Open ISES Tickets 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.
Technical details
A vulnerability exists in Open ISES Tickets versions prior to 3.44.2 due to improper certificate validation in the 'rm/incs/mobile_login.inc.php' component. The application explicitly disables TLS verification by setting 'CURLOPT_SSL_VERIFYPEER' to false and failing to set 'CURLOPT_SSL_VERIFYHOST' during outbound HTTPS requests in the RouteMate login flow. An attacker with a man-in-the-middle (MitM) position can present a forged certificate to intercept or modify encrypted traffic, potentially capturing API keys or session tokens. This issue was addressed in version 3.44.2 by enabling certificate verification by default.
Affected products
- Open ISES Tickets < 3.44.2
Timeline
- 2026-04-01: patched: Fix committed to repository
- 2026-04-02: advisory: Version 3.44.2 released
- 2026-05-21: disclosed: CVE published and NVD record created