# CVE-2026-133240: OpnForm before 2.8.2 SSRF Guard Bypass via PublicWebhookUrl::isPublicIp


- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-m9x4-8p3p-c4xh

## What is CVE-2026-133240?

CVE-2026-133240 is a low-severity vulnerability in OpnForm, published on 19 Nov 2026. 

### Official description

OpnForm before 2.8.2 contains a server-side request forgery vulnerability in PublicWebhookUrl::isPublicIp that fails to reject CGNAT, NAT64 and 6to4 address ranges. Authenticated users can configure webhook, form import or PDF image URLs resolving to these ranges to make the server send HTTPS requests to internal hosts.

Weakness: CWE-918 (Server-Side Request Forgery)

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

1 open source package ship an affected version, including opnform/opnform.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `opnform/opnform` | GitHub | `pkg:github/opnform/opnform` | All versions | 2.8.2 |

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

Upgrade opnform/opnform to 2.8.2 or later.

## Is CVE-2026-133240 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-133240 is a low-severity vulnerability in OpnForm, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-133240 in the wild and no public exploit code.

Affected packages and fixed versions:
- opnform/opnform (GitHub): affected all versions; fixed in 2.8.2

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

## Sources

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

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