# CVE-2026-71247: Documenso - Assistant Recipient Can Forge Another Signer's Signature in Sequential-Signing Documents

> An assistant recipient can forge signatures for other signers in sequential documents due to missing authorization checks in the V1 signing path.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-v65x-57rf-cpg3

## What is CVE-2026-71247?

CVE-2026-71247 is a medium-severity missing authorization vulnerability in documenso, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Documenso's sign-field-with-token.ts, used by the live document-signing UI, allows a recipient with the ASSISTANT role to fetch and complete fields belonging to any later-or-equal-order, not-yet-signed recipient in the same envelope, with no restriction on field type. A newer V2 signing path (sign-envelope-field.ts) explicitly blocks assistants from completing SIGNATURE fields, and the project's own test suite comments confirm this guard is absent from the V1 path used here.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-71247 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71247 is a medium-severity missing authorization vulnerability in documenso, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71247 in the wild and no public exploit code.

Affected product: documenso. 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-71247/ (Markdown: https://insights.sbomify.com/CVE-2026-71247/index.md)
```

## Sources

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

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