Quick answers
- Is CVE-2026-72544 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72544 being exploited in the wild.
- How severe is CVE-2026-72544?
- High severity, with a CVSS score of 7.5, published 11 August 2026.
- Which products and versions are affected?
- OpenSignLabs OpenSign through 2.37.0.
- Is there a fix for CVE-2026-72544?
- 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-72544 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-72544?
- Check whether you run OpenSignLabs OpenSign at an affected version. 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 and integrity verification flaw in the OpenSign triggerevenet Parse cloud function. The function accepts viewer identity and IP address as unauthenticated, caller-supplied parameters, failing to validate the origin or legitimacy of these inputs. An attacker can craft requests to inject arbitrary audit log entries into any signed document's trail, bypassing non-repudiation protections. The vulnerability affects OpenSign through version 2.37.0 and requires only network reachability to the Parse cloud function endpoint; no prior authentication is necessary. Remediation involves implementing proper authentication checks and validating audit trail inputs server-side before recording them.
Affected products
- OpenSignLabs OpenSign through 2.37.0
Timeline
- 2026-08-11: disclosed