API key theft via disabled TLS validation
Published Aug 3, 2026 · Updated Aug 3, 2026
Improper certificate validation in emlog Pro through 2.6.23 allows man-in-the-middle attackers to intercept outbound AI requests. Four request paths in include/service/ai.php disable CURLOPT_SSL_VERIFYPEER and CURLOPT_SSL_VERIFYHOST, causing cURL to accept arbitrary certificates. Exploitation requires a network interception position and configured AI credentials, exposing Bearer API keys and permitting injected AI responses.
Summary
What happened
Improper certificate validation in emlog Pro through 2.6.23 allows man-in-the-middle attackers to intercept outbound AI requests. Four request paths in include/service/ai.php disable CURLOPT_SSL_VERIFYPEER and CURLOPT_SSL_VERIFYHOST, causing cURL to accept arbitrary certificates. Exploitation requires a network interception position and configured AI credentials, exposing Bearer API keys and permitting injected AI responses.
The record
- CVE
- CVE-2026-67598
- Published
- Aug 3, 2026
- Updated
- Aug 3, 2026
- Vendor
- emlog
- Product
- emlog
- Classifications
- CWE-295, T1557
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 3, 2026CVE publishedPublication date reported by the CVE source.
- Aug 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.6.23
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GHSA-hf85-99vj-m4c5 proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo