dbcve.org
Spring AiFramework / library · VMware

CVE-2026-40979

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-28
Fix available
A fix is available. Upgrade to 1.0.6 / 1.1.5 or later.
See remediation →
63/100
Remediation priority · Elevated
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
In Spring AI, having access to a shared environment can expose the ONNX model used by the application. Affected versions: Spring AI: 1.0.0 - 1.0.5 (fixed in 1.0.6), 1.1.0 - 1.1.4 (fixed in 1.1.5)

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 · moderate confidence

Spring AI stores ONNX model files in a manner that allows unauthorized access in shared environments. An attacker with access to the shared environment (e.g., co-located hosting, container escape, or compromised container) can read the ONNX model files, potentially exposing proprietary AI models or sensitive data embedded in them.

MitigationUpgrade Spring AI to version 1.0.6 or 1.1.5. Additionally, ensure ONNX model files are stored in protected directories with appropriate file system permissions, and consider encrypting models at rest if the deployment environment is shared or multi-tenant.

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.6>= 1.1.0, < 1.1.5

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/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. Determine installed Spring AI version
    Inspect your project's dependency management file (pom.xml, build.gradle, or similar) or check the spring-ai-core library JAR manifest for the version number
    Affected if The version is 1.0.0 through 1.0.5, or 1.1.0 through 1.1.4 (any version in the affected ranges)
  2. Identify ONNX model usage
    Search your project for ONNX-related dependencies (search for 'onnx' or 'ort' in pom.xml/build.gradle) and runtime configuration that loads ONNX models via ONNXRuntimeModel or similar classes
    Affected if Your project includes ONNX model dependencies and loads ONNX models at runtime
  3. Locate ONNX model file storage
    Check your application configuration for model storage paths (look for properties like spring.ai.model.options.path, onnx.model.path, or similar ONNX-related configuration), and examine the runtime directory where models are downloaded or stored
    Affected if Model files are stored in a directory accessible to other tenants or containers in the same shared environment
  4. Verify file system permissions on model storage
    Run ls -la on the identified ONNX model directory to inspect owner, group, and world-readable permissions
    Affected if Model files have overly permissive access (world-readable, or accessible by other users/groups in the shared environment)

You are affected if your Spring AI version falls within the affected ranges AND you use ONNX models stored in an unprotected location accessible to other users or containers in the shared environment.

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.6 / 1.1.5 or later
Fixed in 1.0.61.1.5
Interim mitigation

Upgrade Spring AI to version 1.0.6 or 1.1.5. Additionally, ensure ONNX model files are stored in protected directories with appropriate file system permissions, and consider encrypting models at rest if the deployment environment is shared or multi-tenant.

Recommended fix Moderate confidence

Spring AI 1.0.6 or 1.1.5 (or latest stable release)

  1. Identify the current Spring AI version in use by checking pom.xml or build.gradle dependencies
  2. For applications on 1.0.x branch: upgrade Spring AI dependency to version 1.0.6 or later
  3. For applications on 1.1.x branch: upgrade Spring AI dependency to version 1.1.5 or later
  4. Alternatively, upgrade to the latest stable Spring AI release that includes the fix
  5. After upgrading, rebuild and redeploy the application
  6. Review Spring AI release notes for the target version to check for any required configuration changes
Caveat Check Spring AI release notes for migration notes; minor version upgrades typically have minimal breaking changes but review any changed defaults

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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40979 — 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-40979 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