Quick answers
- Is CVE-2026-48246 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48246 being exploited in the wild.
- How severe is CVE-2026-48246?
- Medium severity, with a CVSS score of 5.9, published 21 May 2026.
- Which products and versions are affected?
- Open ISES Tickets before 3.44.2.
- Is there a fix for CVE-2026-48246?
- A patch was published on 2026-04-01: Fix committed to GitHub repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48246 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-48246?
- 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
The vulnerability exists in ajax/reports.php due to the improper configuration of cURL options. Specifically, the application sets CURLOPT_SSL_VERIFYPEER to false and fails to set CURLOPT_SSL_VERIFYHOST when performing Google Maps Directions API lookups during incident report generation. This lack of certificate validation allows an attacker with Man-in-the-Middle (MitM) capabilities to present a forged certificate. Successful exploitation enables the interception, monitoring, or modification of outbound requests and responses, potentially exposing sensitive API keys or session data. The issue is resolved in version 3.44.2.
Affected products
- Open ISES Tickets before 3.44.2
Timeline
- 2026-04-01: patched: Fix committed to GitHub repository
- 2026-04-02: advisory: Release v3.44.2 published
- 2026-05-21: disclosed: CVE-2026-48246 published