# CVE-2026-72544: OpenSignLabs OpenSign - Insufficient Verification of Data Authenticity

> Unauthenticated attackers can forge document audit-trail entries in OpenSign by supplying arbitrary viewer identity and IP parameters, compromising legal non-repudiation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-7j6v-hchx-rmq3

## What is CVE-2026-72544?

CVE-2026-72544 is a high-severity missing authorization vulnerability in OpenSignLabs OpenSign, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An integrity verification vulnerability in OpenSignLabs OpenSign through 2.37.0 allows unauthenticated remote attackers to forge document audit-trail entries via the triggerevent Parse cloud function. The function accepts viewer identity and IP address as caller-supplied parameters without authentication, allowing fabrication of arbitrary audit log entries. An attacker can tamper with the legal audit trail of any signed document, undermining non-repudiation.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-72544?


## How do I fix CVE-2026-72544?

No fix has been published for CVE-2026-72544 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-72544 being exploited?

There is no known exploitation of CVE-2026-72544 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72544 and fix it if it is affected.

What it is: CVE-2026-72544 is a high-severity missing authorization vulnerability in OpenSignLabs OpenSign, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72544 in the wild and no public exploit code.

Affected product: OpenSignLabs OpenSign. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72544/ (Markdown: https://insights.sbomify.com/CVE-2026-72544/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72544
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72544
- OSV: https://osv.dev/vulnerability/CVE-2026-72544

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72544/
Summaries are generated and may contain mistakes; the official description above is the record.