CVE-2026-112040 diem-project CVE debrief

Who should care

Defenders responsible for the diem-project diem deployment should assess exposure and prioritize verification and remediation efforts. Defenders should verify the affected version and apply patches or workarounds to prevent open redirect attacks. The remediation priority is medium due to the publicly disclosed exploit and potential for utilization.

Why it matters

CVE-2026-112040 is a medium-severity vulnerability in diem-project diem that allows open redirect attacks. Defenders should prioritize verifying the affected version and applying patches or workarounds to prevent open redirect attacks.

• Open redirect attacks can lead to phishing attacks or malware distribution.
• Successful exploitation may allow attackers to redirect users to malicious websites.
• Defenders should verify the affected version and apply patches or workarounds to prevent open redirect attacks.
• Remediation priority is medium due to the publicly disclosed exploit and potential for utilization.

Technical summary

The vulnerability affects the diem-project diem up to version 116974edfb9a5b8bd69cb13586dc62bcdbb485ad. The manipulation of the argument Referer in the file dmCorePlugin/plugins/dmUserPlugin/modules/dmUser/lib/BasedmUserActions.class.php of the component Sign-In causes open redirect. Defenders should prioritize verifying the affected version and applying patches or workarounds to prevent open redirect attacks. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized.

Defensive priority

Defenders should prioritize verifying the affected version and applying patches or workarounds to prevent open redirect attacks.

Recommended defensive actions

• Verify the affected version of diem-project diem and apply patches or workarounds to prevent open redirect attacks.
• Monitor for potential open redirect attacks targeting the Sign-In component.
• Implement additional security measures to prevent exploitation, such as validating user input and restricting access to sensitive areas.
• 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 vulnerability was publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet. Defenders should verify the affected version and apply patches or workarounds to prevent open redirect attacks. The CVE record was published on 2026-10-19T01:45:16.543Z and has not been modified since then.

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.