dbcve.org
Spring AiFramework / library · VMware

CVE-2026-22742

HIGH · 8.6 CVSS v3.1 Published 2026-03-27
Fix available
A fix is available. Upgrade to 1.0.5 / 1.1.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Spring AI's BedrockProxyChatModel in spring-ai-bedrock-converse contains an SSRF vulnerability where insufficient validation of user-supplied media URLs in multimodal messages allows attackers to induce the server to make HTTP requests to internal or external destinations by providing malicious URLs.

MitigationUpgrade Spring AI to version 1.0.5 or 1.1.4 or later which contains the fix. Additionally, implement strict URL validation and allowlist filtering for media URLs before processing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Spring AiFramework / library
Affected:>= 1.0.0, < 1.0.5>= 1.1.0, < 1.1.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Spring AI version
    Check your project's dependency management file (Maven pom.xml, Gradle build.gradle) or the deployed spring-ai-core JAR manifest for the exact version number
    Affected if The installed version is 1.0.0 through 1.0.4, or 1.1.0 through 1.1.3
  2. Verify Bedrock converse module presence
    Inspect your project's dependencies for spring-ai-bedrock-converse or spring-ai-aws (the module containing BedrockProxyChatModel)
    Affected if The spring-ai-bedrock-converse dependency is present in your project
  3. Confirm BedrockProxyChatModel usage
    Search codebase for imports or references to BedrockProxyChatModel class, or review Bean configuration files where chat models are defined
    Affected if BedrockProxyChatModel is instantiated or used as a chat model bean
  4. Check for multimodal message handling
    Review application code that processes multimodal (image, audio, video) messages, particularly code that accepts user-supplied URLs in ChatMessage objects
    Affected if The application accepts or processes media URLs from user input in chat interactions

You are affected if your Spring AI version is vulnerable (1.0.0-1.0.4 or 1.1.0-1.1.3) AND the BedrockProxyChatModel is in use with multimodal message capabilities that accept external URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.5 / 1.1.4 or later
Fixed in 1.0.51.1.4
Interim mitigation

Upgrade Spring AI to version 1.0.5 or 1.1.4 or later which contains the fix. Additionally, implement strict URL validation and allowlist filtering for media URLs before processing.

Recommended fix High confidence

spring-ai-bedrock-converse version 1.0.5 or 1.1.4 (depending on major version branch)

  1. Check the current Spring AI version in use (examine pom.xml or build.gradle for spring-ai-bedrock-converse dependency)
  2. Upgrade spring-ai-bedrock-converse dependency to version 1.0.5 for 1.0.x line users, or 1.1.4 for 1.1.x line users
  3. Verify the upgrade by rebuilding the project and running tests
  4. Ensure no runtime errors related to BedrockProxyChatModel after upgrade
Caveat Minor version upgrades may include API changes; test thoroughly in non-production first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Ai Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22742 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22742 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data