How severe is GHSA-r5hp-3cgj-j6xv?

GHSA-r5hp-3cgj-j6xv has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-r5hp-3cgj-j6xv?

GHSA-r5hp-3cgj-j6xv affects the following packages: org.springframework.ai:spring-ai-transformers (Maven), org.springframework.ai:spring-ai-transformers (Maven). Ecosystems affected: Maven.

How do I fix GHSA-r5hp-3cgj-j6xv?

Update org.springframework.ai:spring-ai-transformers to 1.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r5hp-3cgj-j6xv is resolved across your whole dependency graph.

How do I detect GHSA-r5hp-3cgj-j6xv in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.ai:spring-ai-transformers. 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.

How do I mitigate GHSA-r5hp-3cgj-j6xv if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-r5hp-3cgj-j6xv?

O3 pinpoints whether GHSA-r5hp-3cgj-j6xv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-r5hp-3cgj-j6xv actively exploited in the wild?

No public exploit code has been indexed for GHSA-r5hp-3cgj-j6xv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-r5hp-3cgj-j6xv?

GHSA-r5hp-3cgj-j6xv is classified as CWE-377 (CWE-377). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-r5hp-3cgj-j6xv published, and has it been updated?

GHSA-r5hp-3cgj-j6xv was published on April 28, 2026 and was last updated on May 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-r5hp-3cgj-j6xv

MEDIUM

GHSA-r5hp-3cgj-j6xv is a medium-severity (CVSS 6.1) CWE-377 vulnerability in org.springframework.ai:spring-ai-transformers. O3 Security confirms whether GHSA-r5hp-3cgj-j6xv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Spring AI's ONNX model cache defaults to world-writable predictable /tmp directory

Also known asCVE-2026-40979

Published

Apr 28, 2026

Updated

May 6, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

☕org.springframework.ai:spring-ai-transformers☕org.springframework.ai:spring-ai-transformers

Real-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

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)

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.ai:spring-ai-transformers`	≥ 1.0.0&&< 1.0.6	1.0.6
☕Maven	`org.springframework.ai:spring-ai-transformers`	≥ 1.1.0&&< 1.1.5	1.1.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.ai:spring-ai-transformers. 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-transformers to 1.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r5hp-3cgj-j6xv 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-r5hp-3cgj-j6xv 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-r5hp-3cgj-j6xv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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)

O3 Security · Impact-Aware SCA

Is GHSA-r5hp-3cgj-j6xv in your dependencies?

O3 detects GHSA-r5hp-3cgj-j6xv across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works