GHSA-mhrg-94vw-45c5 is a high-severity (CVSS 8.6) Server-Side Request Forgery (SSRF) vulnerability in org.springframework.ai:spring-ai-bedrock-converse. O3 Security confirms whether GHSA-mhrg-94vw-45c5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Spring AI: Insufficient Validation causes SSRF when processing multimodal messages with user-supplied URLs
Real-World Exposure
org.springframework.ai:spring-ai-bedrock-converse☕org.springframework.ai:spring-ai-bedrock-converseReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Spring AI's spring-ai-bedrock-converse contains a Server-Side Request Forgery (SSRF) vulnerability in BedrockProxyChatModel when processing multimodal messages that include user-supplied media URLs. Insufficient validation of those URLs allows an attacker to induce the server to issue HTTP requests to unintended internal or external destinations.
This issue affects Spring AI: from 1.0.0 before 1.0.5, from 1.1.0 before 1.1.4.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.ai:spring-ai-bedrock-converse | ≥ 1.0.0-M5&&< 1.0.5 | 1.0.5 |
| ☕Maven | org.springframework.ai:spring-ai-bedrock-converse | ≥ 1.1.0-M1&&< 1.1.4 | 1.1.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.ai:spring-ai-bedrock-converse. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.springframework.ai:spring-ai-bedrock-converse to 1.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mhrg-94vw-45c5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-mhrg-94vw-45c5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-mhrg-94vw-45c5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-mhrg-94vw-45c5 in your dependencies?
O3 detects GHSA-mhrg-94vw-45c5 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.