SSRF via unchecked src URL fetch
Published Aug 17, 2026 · Updated Aug 18, 2026
Server-side request forgery in get_images in Junpei Kawamoto mcp-florence2 0.3.13 and earlier allows attackers to send HTTP requests via src. When ocr or caption receives an HTTP(S) src value, get_images checks only the string prefix and passes the full user-controlled URL to requests.get() with no destination allowlist, IP-range filtering, redirect control, or timeout. Exposure depends on whether an MCP client or connected agent can invoke those tools with a controlled src value; successful exploitation lets the server reach internal services or metadata endpoints and can disclose image or PDF content returned from reachable hosts.
Summary
What happened
Server-side request forgery in get_images in Junpei Kawamoto mcp-florence2 0.3.13 and earlier allows attackers to send HTTP requests via src. When ocr or caption receives an HTTP(S) src value, get_images checks only the string prefix and passes the full user-controlled URL to requests.get() with no destination allowlist, IP-range filtering, redirect control, or timeout. Exposure depends on whether an MCP client or connected agent can invoke those tools with a controlled src value; successful exploitation lets the server reach internal services or metadata endpoints and can disclose image or PDF content returned from reachable hosts.
The record
- CVE
- CVE-2026-19984
- Published
- Aug 17, 2026
- Updated
- Aug 18, 2026
- Vendor
- Junpei Kawamoto
- Product
- mcp-florence2
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 17, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.3.0
- Affected versionversion=0.3.1
- Affected versionversion=0.3.10
- Affected versionversion=0.3.11
- Affected versionversion=0.3.12
- Affected versionversion=0.3.13
- Affected versionversion=0.3.2
- Affected versionversion=0.3.3
- Affected versionversion=0.3.4
- Affected versionversion=0.3.5
- Affected versionversion=0.3.6
- Affected versionversion=0.3.7
- Affected versionversion=0.3.8
- Affected versionversion=0.3.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- SSRF proof of concept in GitHub Issue #59proof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo