CVE-2026-48246
Deferred Deferred - Pending Action
Open ISES Tickets TLS Certificate Verification Bypass

Publication date: 2026-05-21

Last updated on: 2026-05-21

Assigner: VulnCheck

Description
Open ISES Tickets before 3.44.2 disables TLS certificate verification in ajax/reports.php by setting CURLOPT_SSL_VERIFYPEER to false (and not setting CURLOPT_SSL_VERIFYHOST) when issuing outbound HTTPS requests for Google Maps Directions API lookups during incident report generation. 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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-21
Last Modified
2026-05-21
Generated
2026-06-11
AI Q&A
2026-05-21
EPSS Evaluated
2026-06-10
NVD
EUVD
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-295 The product does not validate, or incorrectly validates, a certificate.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in Open ISES Tickets versions before 3.44.2, where TLS certificate verification is disabled in the ajax/reports.php file during outbound HTTPS requests to the Google Maps Directions API.

Specifically, the software sets the CURLOPT_SSL_VERIFYPEER option to false and does not set CURLOPT_SSL_VERIFYHOST, which means it does not properly verify the authenticity of the TLS certificates.

As a result, 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 HTTPS requests and responses, including sensitive data such as API keys or session information.

Impact Analysis

This vulnerability can allow an attacker to perform a man-in-the-middle attack by intercepting and potentially altering the data exchanged between the server and the Google Maps Directions API.

  • Exposure of sensitive information such as API keys or session data.
  • Modification of the data in transit, which could lead to incorrect incident reports or other malicious outcomes.
  • Compromise of the integrity and confidentiality of communications between the server and external services.
Detection Guidance

This vulnerability can be detected by inspecting the source code of the Open ISES Tickets application, specifically the ajax/reports.php file, to check if the TLS certificate verification options are improperly set. Look for the use of CURLOPT_SSL_VERIFYPEER set to false and the absence of CURLOPT_SSL_VERIFYHOST when making HTTPS requests.

On the system or network level, monitoring outbound HTTPS requests to the Google Maps Directions API and checking for signs of intercepted or modified traffic could indicate exploitation.

Suggested commands to detect the vulnerability include:

  • Use grep or similar tools to search for the relevant curl options in the codebase: grep -r "CURLOPT_SSL_VERIFYPEER" /path/to/open-ises-tickets/
  • Use network packet capture tools like tcpdump or Wireshark to monitor HTTPS traffic from the server to the Google Maps Directions API endpoint for anomalies.
Mitigation Strategies

The immediate mitigation step is to upgrade Open ISES Tickets to version 3.44.2 or later, where the TLS certificate verification is properly enabled.

If upgrading is not immediately possible, manually modify the ajax/reports.php file to ensure that CURLOPT_SSL_VERIFYPEER is set to true and CURLOPT_SSL_VERIFYHOST is properly set when making HTTPS requests.

Additionally, monitor network traffic for suspicious activity and consider restricting network access to trusted endpoints to reduce the risk of man-in-the-middle attacks.

Compliance Impact

This vulnerability disables TLS certificate verification, allowing an attacker to intercept or modify sensitive data such as API keys or session information during transmission.

Such interception or exposure of sensitive data can lead to violations of data protection requirements mandated by standards and regulations like GDPR and HIPAA, which require secure transmission and protection of personal and sensitive information.

Therefore, the vulnerability negatively impacts compliance by undermining the confidentiality and integrity of data in transit.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-48246. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart