# CVE-2026-19984: jkawamoto mcp-florence2 __init__.py get_images server-side request forgery

> Remote attackers can exploit the get_images function to perform server-side request forgery, requiring mitigation via an SSRF-safe proxy.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 17 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-xvcx-vvm4-3qwc

## What is CVE-2026-19984?

CVE-2026-19984 is a medium-severity server-side request forgery vulnerability in jkawamoto mcp-florence2, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw has been found in jkawamoto mcp-florence2 up to 0.3.13. Affected by this issue is the function get_images of the file src/mcp_florence2/__init__.py. This manipulation of the argument src causes server-side request forgery. The attack may be initiated remotely. The exploit has been published and may be used. It is recommended to change the configuration settings. The vendor explains: "For deployments where SSRF protection is required, I recommend routing all HTTP(S) requests through an SSRF-safe proxy server. This approach mitigates the vulnerability without requiring changes to the mcp-florence2 source code."

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

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


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

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

## Is CVE-2026-19984 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19984 is a medium-severity server-side request forgery vulnerability in jkawamoto mcp-florence2, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19984 exists.

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

## Sources

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

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