PatchSiren cyber security CVE debrief
CVE-2026-92794 OpenSignLabs CVE debrief
OpenSign through 2.41.3 has an information disclosure vulnerability in the getDocument cloud function when one-time-password verification is disabled. This allows attackers to retrieve complete document details, including signers' information, sender identity, and valid download tokens, without authentication, by supplying a document identifier from guest signing links.
- Vendor
- OpenSignLabs
- Product
- OpenSign
- CVSS
- HIGH 8.7
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-16
- Original CVE updated
- 2026-09-22
- Advisory published
- 2026-09-16
- Advisory updated
- 2026-09-22
Who should care
Defenders responsible for OpenSign deployments should assess exposure and prioritize verification of the getDocument cloud function. Roles include security teams, IT administrators, and developers using OpenSign.
Why it matters
CVE-2026-92794 is a high-severity information disclosure vulnerability in OpenSign through 2.41.3. Defenders should prioritize verifying and potentially upgrading to a fixed version, restrict access to sensitive document identifiers, and assess exposure of the getDocument cloud function.
- Defenders must verify OpenSign version and assess exposure of the getDocument cloud function.
- If one-time-password verification is disabled, document identifiers from guest signing links should be treated as potentially sensitive.
- Remediation priority follows from verifying and upgrading to a fixed version if available.
- Exposure requires verification from official sources.
Technical summary
The OpenSign cloud function getDocument fails to validate caller identity when one-time-password verification is disabled. This allows attackers to supply a document identifier from guest signing links to retrieve complete document details, including all signers' information, sender identity, and valid download tokens without authentication. Affected product deployments should be verified for exposure, and defenders should consider upgrading to a fixed version if available, restrict access to sensitive document identifiers, and assess the impact on their security posture.
Defensive priority
Defenders should prioritize verifying the use of OpenSign version 2.41.3 or earlier and assess exposure of the getDocument cloud function. If one-time-password verification is disabled, defenders should treat document identifiers from guest signing links as potentially sensitive and restrict access accordingly. Remediation priority follows from verifying and upgrading to a fixed version if available.
Recommended defensive actions
- Verify OpenSign version and assess exposure of the getDocument cloud function
- Restrict access to document identifiers from guest signing links if one-time-password verification is disabled
- Consider upgrading to a fixed version if available
- 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 NVD entry provide details on the vulnerability in OpenSign through 2.41.3. The vulnerability allows for information disclosure via the getDocument cloud function. Official sources include CVE Program and NIST NVD.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-92794 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-92794
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-92794 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-92794
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/OpenSignLabs/OpenSign
-
Source reference
Unverified legacy reference
URL: https://github.com/OpenSignLabs/OpenSign/blob/v2.41.0/apps/OpenSignServer/cloud/parsefunction/getDocument.js
-
Source reference
Unverified legacy reference
URL: https://github.com/OpenSignLabs/OpenSign/issues/2218
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/opensign-through-2.41.3-information-disclosure-via-getdocument
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.