PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-112043 calcom CVE debrief

A weakness has been identified in calcom cal.com and cal.diy up to 6.2.0. Impacted is the function createWebhookProcedure of the file packages/trpc/server/routers/viewer/webhook/util.ts of the component Webhook Handler. Executing a manipulation of the argument ID can lead to authorization bypass. It is possible to launch the attack remotely. The pull request to fix this issue awaits acceptance.

Vendor
calcom
Product
cal.com
CVSS
MEDIUM 5.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-19
Original CVE updated
2026-10-19
Advisory published
2026-10-19
Advisory updated
2026-10-19

Who should care

Defenders responsible for calcom cal.com and cal.diy deployments should assess exposure and verify the affected versions. Defenders should also prioritize verifying affected versions and assessing exposure, as the vulnerability allows for remote authorization bypass. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review and verify the affected versions and assess exposure to prevent attacks.

Why it matters

CVE-2026-112043 is a medium-severity vulnerability in calcom cal.com and cal.diy that allows for remote authorization bypass. Defenders should prioritize verifying affected versions and assessing exposure.

  • Defenders should verify the affected versions to determine if exposure exists
  • Remote authorization bypass could lead to unintended access

Technical summary

The vulnerability is located in the createWebhookProcedure function of the Webhook Handler component in calcom cal.com and cal.diy up to 6.2.0. A manipulation of the argument ID can lead to authorization bypass, allowing for remote attacks. This vulnerability allows for remote authorization bypass, and defenders should prioritize verifying affected versions and assessing exposure to prevent potential attacks. The affected product or component is calcom cal.com and cal.diy up to 6.2.0, and the vulnerability class is authorization bypass.

Defensive priority

Defenders should prioritize verifying the affected versions and assessing exposure, as the vulnerability allows for remote authorization bypass.

Recommended defensive actions

  • Verify the version of calcom cal.com and cal.diy to determine if it is affected by the vulnerability
  • Assess exposure to the Webhook Handler component
  • Review the createWebhookProcedure function for potential authorization bypass vulnerabilities
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but the scope of affected versions and potential impact require further verification. Defenders should verify the affected versions and assess exposure. The vulnerability allows for remote authorization bypass, and defenders should prioritize verifying affected versions and assessing exposure.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-112043 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-112043

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-112043 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-112043

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental 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.