{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67598 exists.","fix":"No fix has been published for CVE-2026-67598 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-67598 is a critical vulnerability in emlog, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-67598 and fix it if it is affected.\n\nWhat it is: CVE-2026-67598 is a critical vulnerability in emlog, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67598 exists.\n\nAffected product: emlog. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-67598/ (Markdown: https://insights.sbomify.com/CVE-2026-67598/index.md)","id":"CVE-2026-67598","markdown":"https://insights.sbomify.com/CVE-2026-67598/index.md","name":"CVE-2026-67598","record":{"aliases":["GHSA-hf85-99vj-m4c5","GHSA-j63f-h5jj-qrf5"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Emlog Pro blog","requires_auth":"none","summary":"Attackers can intercept HTTPS traffic to extract API keys and inject malicious AI responses due to disabled TLS certificate validation in Emlog Pro.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"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 CURLOPT_SSL_VERIFYPEER and CURLOPT_SSL_VERIFYHOST 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 query_database and update_config tool handlers.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-08-06","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-06T10:35:31Z","kind":"github_poc","ref":"https://github.com/IlhomjonR/CVE-2026-67598","stars":0,"title":"CVE-2026-67598 — Emlog Pro: disabled TLS certificate validation in AI assistant (MITM → API-key theft). CWE-295, CVSS 9.1. Reported by @IlhomjonR."}],"tier":"weaponised"},"has_fix":false,"headline":"Emlog Pro 2.6.23 TLS Certificate Validation Disabled in ai.php","id":"CVE-2026-67598","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"ClearOS 7.9 OS Command Injection via Log Viewer filter parameter","id":"CVE-2026-67599"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2026-67597"},"products":["emlog"],"published":"2026-08-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-14","vendors":["emlog"]},"summary":"Attackers can intercept HTTPS traffic to extract API keys and inject malicious AI responses due to disabled TLS certificate validation in Emlog Pro.","url":"https://insights.sbomify.com/CVE-2026-67598/"}