CVE-2026-67598: Emlog Pro 2.6.23 TLS Certificate Validation Disabled in ai.php

Published Aug 3, 2026
·
Updated

Emlog Pro through 2.6.23 contains a disabled TLS certificate validation vulnerability in include/service/ai.php that allows network-adjacent attackers to intercept outbound HTTPS requests to configured LLM providers by presenting arbitrary TLS certificates, as CURLOPTSSLVERIFYPEER and CURLOPTSSLVERIFYHOST are unconditionally disabled across sendStream(), sendImageRequest(), send(), and fetchSearchHtml() with no option to re-enable verification. Attackers can perform man-in-the-middle interception to extract Authorization Bearer API keys from every AI request and inject crafted AI responses that may be acted upon by the tool-call execution pipeline, including the querydatabase and updateconfig tool handlers.

Affected Software

1 affected component
Emlog Pro Emlog Pro<=2.6.23

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Emlog Pro to a version that resolves this vulnerability.

    Fixed in 2.6.23
  2. Configuration

    Enable TLS certificate verification in include/service/ai.php; do not unconditionally disable CURLOPT_SSL_VERIFYPEER (it is described as unconditionally disabled across sendStream(), sendImageRequest(), send(), and fetchSearchHtml()).

    Emlog Pro (include/service/ai.php) CURLOPT_SSL_VERIFYPEER = enabled
  3. Configuration

    Enable TLS hostname verification in include/service/ai.php; do not unconditionally disable CURLOPT_SSL_VERIFYHOST (it is described as unconditionally disabled across sendStream(), sendImageRequest(), send(), and fetchSearchHtml()).

    Emlog Pro (include/service/ai.php) CURLOPT_SSL_VERIFYHOST = enabled
  4. Compensating control

    Use a network control to prevent network-adjacent man-in-the-middle interception of outbound HTTPS requests to the configured LLM providers (e.g., restrict egress/route traffic so attackers cannot present arbitrary TLS certificates).

  5. Operational

    If Authorization Bearer API keys may have been intercepted before TLS verification was corrected, rotate those exposed keys.

Event History

Aug 3, 2026
CVE Published
via MITRE·07:02 PM
Data Sourced
via MITRE·07:02 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:17 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-67598?

CVE-2026-67598 has a high severity score of 7.4.

2

How do I fix CVE-2026-67598?

To fix CVE-2026-67598, update Emlog Pro to a version above 2.6.23 that enables TLS certificate validation.

3

What vulnerabilities are associated with CVE-2026-67598?

CVE-2026-67598 allows network-adjacent attackers to intercept outbound HTTPS requests due to disabled TLS certificate validation.

4

Who is affected by CVE-2026-67598?

CVE-2026-67598 affects users of Emlog Pro version 2.6.23 and earlier.

5

What components are involved in CVE-2026-67598?

CVE-2026-67598 involves the ai.php file in the Emlog Pro application.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203