# CVE-2026-114064: Snipe-IT before 8.7.0 SSRF Port Scanning via Webhook Testing Endpoint


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:L/SC:L/SI:N/SA:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-8hr2-qw73-v566, GHSA-wqfr-w9hp-c7v6

## What is CVE-2026-114064?

CVE-2026-114064 is a medium-severity vulnerability in grokability snipe-it, published on 21 Oct 2026. 

### Official description

Snipe-IT before 8.7.0 contains a server-side request forgery vulnerability in the webhook testing feature that allows super-admin users to probe internal network addresses, including loopback and RFC1918 ranges. Attackers can point webhooks at internal hosts and ports, then compare 4xx versus 5xx responses from Test Webhooks to map open ports and active hosts.

Weakness: CWE-203 (Observable Discrepancy)

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


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

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

## Is CVE-2026-114064 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114064 is a medium-severity vulnerability in grokability snipe-it, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114064 exists.

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

## Sources

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

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