# CVE-2026-75106: OpnForm Editable Submission Secret Derivation via Empty Hashids Salt

> Unauthenticated attackers can predict submission secrets to read or modify other users' form data due to weak hash derivation.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-3j74-gjwg-45jm

## What is CVE-2026-75106?

CVE-2026-75106 is a critical vulnerability in OpnForm, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpnForm derives editable-submission secrets from sequential row identifiers using Hashids with an empty default salt, allowing unauthenticated attackers to compute hashes for any submission. Attackers can read other respondents' full submission data through the submission-fetch endpoint or overwrite submissions by supplying predicted hashes to the answer endpoint.

Weakness: CWE-340 (Generation of Predictable Numbers or Identifiers)

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


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

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

## Is CVE-2026-75106 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75106 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75106 is a critical vulnerability in OpnForm, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75106 exists.

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

## Sources

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

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