CVE-2026-48249: Open ISES Tickets < 3.44.2 Disabled TLS Certificate Verification in rm/incs/mobile_login.inc.php
Open ISES Tickets before 3.44.2 disables TLS certificate verification in rm/incs/mobile_login.inc.php by setting CURLOPT_SSL_VERIFYPEER to false (and not setting CURLOPT_SSL_VERIFYHOST) when issuing outbound HTTPS requests issued during the mobile (RouteMate) login flow. An attacker positioned on the network path between the server and the remote endpoint can present a forged certificate to intercept, monitor, or modify the request and response, including any API keys or session-bearing data in transit.
Security readout for executives and security teams
Plain-English summary
Open ISES Tickets before 3.44.2 may trust forged TLS certificates during RouteMate mobile login. A network-positioned attacker could intercept or alter authentication traffic, potentially exposing API keys or session data. The weakness affects confidentiality and integrity but requires access to the network path.
Executive priority
Treat this as a high-priority upgrade for exposed or actively used RouteMate deployments. Accelerate remediation where authentication traffic crosses shared, externally managed, or otherwise untrusted networks. Investigate and rotate credentials if interception may have occurred.
Technical view
The RouteMate login code in rm/incs/mobile_login.inc.php disables CURLOPT_SSL_VERIFYPEER and does not configure CURLOPT_SSL_VERIFYHOST for outbound HTTPS requests. This creates CWE-295 improper certificate validation. The supplied CVSS 4.0 score is 8.2, reflecting potentially high confidentiality and integrity impact with high attack complexity.
Likely exposure
Exposure is limited to Open ISES Tickets versions before 3.44.2 using the RouteMate mobile login flow. Risk is greatest where an attacker can influence DNS, routing, proxies, Wi-Fi, or another segment between the Tickets server and its remote endpoint.
Exploitation context
The supplied record is not listed in CISA KEV, and the source bundle provides no evidence of active exploitation or a public exploit. Successful abuse requires a network-path position and a forged certificate accepted by the vulnerable server-side request.
Researcher notes
The vulnerable behavior is specifically identified in rm/incs/mobile_login.inc.php. The cited commit and 3.44.2 release are the supplied remediation evidence. The unusual affected-version metadata lists "0," but the narrative explicitly states versions before 3.44.2; validate local versions against vendor materials.
Mitigation direction
Upgrade Open ISES Tickets to version 3.44.2 or later.
Prioritize systems using the RouteMate mobile login flow.
Protect outbound traffic and restrict untrusted access to relevant network paths.
Review vendor release notes and patch details before deployment.
Rotate exposed API keys or sessions if interception is suspected.
Validation and detection
Inventory Open ISES Tickets deployments and record their exact versions.
Confirm every deployment is running version 3.44.2 or later.
Verify RouteMate login requests perform peer and hostname certificate validation.
Review network and application logs for unexpected endpoints, certificates, or authentication anomalies.
Test the mobile login flow after upgrading without bypassing TLS validation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-295: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-295 · source CWE mapping
Improper Certificate Validation
Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.