Quick answers
- Is CVE-2026-92794 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92794 being exploited in the wild.
- How severe is CVE-2026-92794?
- High severity, with a CVSS score of 7.5, published 16 September 2026.
- Which products and versions are affected?
- OpenSign OpenSign through 2.41.3.
- Is there a fix for CVE-2026-92794?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-92794 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-92794?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authentication bypass in the getDocument cloud function (Parse cloud function). The root cause is improper conditional logic: when IsEnableOTP is false, the function returns the full document without any access control checks, whereas it should validate caller identity regardless of OTP settings. The attack vector is network-based and requires no authentication—an attacker with knowledge of a document identifier (obtainable from a guest signing link) can call the function directly to retrieve all document metadata, signer details, sender identity, and download tokens. The fix is to apply consistent access control validation regardless of OTP enablement status.
Affected products
- OpenSign OpenSign through 2.41.3
Timeline
- 2026-09-16: disclosed