Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-112037 Overview
CVE-2026-112037 is an improper certificate validation flaw [CWE-287] affecting the dmCorePlugin/lib/vendor/gapi/gapi.class.php file in the Google Analytics Client component of the diem-project diem content management system. The affected code path up to commit 116974edfb9a5b8bd69cb13586dc62bcdbb485ad does not correctly validate TLS certificates when communicating with Google Analytics endpoints. An attacker on a network path between the Diem instance and the remote service can leverage this gap to tamper with analytics traffic. Diem uses a rolling release model, so there is no fixed version boundary for the affected or patched code.
Critical Impact
Remote attackers positioned on the network path can bypass certificate validation to intercept or manipulate Google Analytics API traffic, affecting integrity of outbound analytics data.
Affected Products
- diem-project diem CMS up to commit 116974edfb9a5b8bd69cb13586dc62bcdbb485ad
- Component: Google Analytics Client (gapi.class.php)
- Rolling-release branches with no fixed version boundary
Discovery Timeline
- 2026-10-19 - CVE-2026-112037 published to NVD
- 2026-10-19 - Last updated in NVD database
Technical Details for CVE-2026-112037
Vulnerability Analysis
The vulnerability resides in the Google Analytics client library bundled with Diem under dmCorePlugin/lib/vendor/gapi/gapi.class.php. The HTTPS client used to reach Google Analytics endpoints does not enforce proper verification of the remote server's X.509 certificate. As a result, forged or self-signed certificates presented by an attacker in a privileged network position are accepted by the client. The weakness is categorized under improper authentication [CWE-287] because certificate validation is a core authentication mechanism for TLS peers.
Successful exploitation requires an attacker to control or intercept the network path between the Diem server and the Google Analytics host. Because the attack chain depends on positioning and TLS interception tooling, the exploitability is rated as high complexity and difficult. The published vector impacts integrity only, with no direct effect on confidentiality or availability of the Diem application itself.
Root Cause
The gapi.class.php HTTPS transport logic omits strict certificate verification options or fails to validate the certificate chain and hostname when connecting to Google Analytics endpoints. Legacy PHP stream and cURL defaults in this vendored library do not enforce peer verification, allowing TLS sessions to proceed against untrusted certificates.
Attack Vector
The attack is launched remotely over the network. An attacker who can perform an on-path interception, such as a rogue upstream router, compromised proxy, or hostile Wi-Fi segment used by the Diem server, presents an attacker-controlled certificate for the Google Analytics host. The vulnerable client completes the TLS handshake and transmits analytics requests, which the attacker can read or modify. There is no authentication or user interaction required on the Diem side.
No verified proof-of-concept code is published alongside the advisory. The flaw is described in the public GitHub Issue #454 Discussion and tracked in the VulDB CVE-2026-112037 Entry.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-112037
Indicators of Compromise
- Outbound HTTPS connections from Diem hosts to Google Analytics endpoints that terminate at unexpected IP addresses or autonomous systems.
- TLS sessions to www.google-analytics.com presenting certificates not issued by Google Trust Services or other legitimate roots.
- Unexpected gapi.class.php HTTP error logs indicating certificate warnings or retries.
Detection Strategies
- Inspect network traffic from web servers running Diem for TLS fingerprints and certificate issuers that deviate from Google's expected certificate chain.
- Review the vendored gapi.class.php file for calls that disable CURLOPT_SSL_VERIFYPEER or CURLOPT_SSL_VERIFYHOST, or that use stream contexts without verify_peer => true.
- Correlate PHP error logs with egress proxy logs to flag HTTPS requests that bypass certificate validation.
Monitoring Recommendations
- Alert when Diem servers initiate TLS sessions to Google Analytics hostnames resolving outside Google's published IP ranges.
- Monitor for configuration changes to the dmCorePlugin/lib/vendor/gapi/ directory and track commits that modify TLS options.
- Baseline normal analytics traffic volumes and alert on sudden drops or anomalies that may indicate interception or tampering.
How to Mitigate CVE-2026-112037
Immediate Actions Required
- Audit the deployed gapi.class.php and enable strict certificate verification in all HTTPS calls made by the Google Analytics client.
- Route Diem outbound traffic through a trusted egress proxy that enforces TLS validation and certificate pinning for Google endpoints.
- Restrict network paths from Diem servers to Google Analytics so that only known, trusted upstream routes are used.
Patch Information
As of the NVD publication on 2026-10-19, the diem-project maintainers have not responded to the issue report, and no official patched commit has been identified. Because Diem is distributed as a rolling release, administrators should track the GitHub Diem Project Repository and the GitHub Issue #454 Discussion for upstream fixes. Operators can apply a local patch to gapi.class.php to force certificate verification until an upstream change is published.
Workarounds
- Replace the vendored gapi.class.php client with a maintained HTTP library that validates certificates by default.
- Disable the Google Analytics integration in Diem if analytics telemetry is not required for the deployment.
- Enforce outbound TLS inspection or pinning at a gateway so that only valid Google certificates are permitted on egress.
# Configuration example: enforce strict TLS verification in PHP cURL defaults
# Add to php.ini or an auto_prepend file loaded by Diem
curl.cainfo = "/etc/ssl/certs/ca-certificates.crt"
openssl.cafile = "/etc/ssl/certs/ca-certificates.crt"
# When patching gapi.class.php, ensure these cURL options are set:
# curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, true);
# curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 2);
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

