CVE-2026-112037 diem-project CVE debrief

Who should care

Defenders responsible for systems using diem-project diem should assess exposure and verify the certificate validation in the Google Analytics Client gapi.class.php. This includes reviewing the current implementation of the Google Analytics Client and ensuring that it properly validates SSL/TLS certificates. Additionally, defenders should consider the potential impact of this vulnerability on their systems and prioritize remediation efforts accordingly.

Why it matters

Defenders should prioritize verifying the certificate validation in the Google Analytics Client gapi.class.php and assessing exposure in their systems. The exploit has been published and may be used, but no version details for affected or updated releases are available.

• Verify certificate validation in Google Analytics Client gapi.class.php
• Assess exposure in systems using diem-project diem
• Monitor for potential exploitation attempts

Technical summary

The vulnerability is located in dmCorePlugin/lib/vendor/gapi/gapi.class.php of the diem-project diem product. It allows for improper certificate validation, which can be exploited remotely with high complexity. The issue arises from inadequate validation of SSL/TLS certificates used by the Google Analytics Client. This could potentially allow attackers to intercept or manipulate data. Defenders should prioritize verifying the certificate validation in the Google Analytics Client gapi.class.php and assessing exposure in their systems.

Defensive priority

Defenders should prioritize verifying the certificate validation in the Google Analytics Client gapi.class.php and assessing exposure in their systems.

Recommended defensive actions

• Verify the certificate validation in the Google Analytics Client gapi.class.php
• Assess exposure in systems using diem-project diem
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details about the vulnerability. However, the corpus does not establish versions, exploitation, impact, or remediation, which require verification from the supplied official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.