# CVE-2026-9370: ulisesbocchio jasypt-spring-boot Password Hash SimpleGCMConfig.java getSecretKeySaltGenerator hash predictable salt

> Attackers can exploit predictable salts in jasypt-spring-boot to weaken password hashing, potentially exposing encrypted data.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-jgj7-c8vj-w563

## What is CVE-2026-9370?

CVE-2026-9370 is a medium-severity vulnerability in ulisesbocchio jasypt-spring-boot, published on 24 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A weakness has been identified in ulisesbocchio jasypt-spring-boot up to 3.0.5/4.0.4. Affected by this vulnerability is the function getSecretKeySaltGenerator of the file jasypt-spring-boot/src/main/java/com/ulisesbocchio/jasyptspringboot/encryptor/SimpleGCMConfig.java of the component Password Hash Handler. Executing a manipulation can lead to use of a one-way hash with a predictable salt. The attack can be launched remotely. The attack requires a high level of complexity. The exploitation appears to be difficult. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-760 (Use of a One-Way Hash with a Predictable Salt), CWE-759 (Use of a One-Way Hash without a Salt)

## Which versions are affected by CVE-2026-9370?

4 open source packages ship an affected version, including com.github.ulisesbocchio:jasypt-spring-boot and com.github.ulisesbocchio:jasypt-spring-boot-starter.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.github.ulisesbocchio:jasypt-spring-boot` | Maven | From 3.0.0 to 4.0.4 | None |
| `com.github.ulisesbocchio:jasypt-spring-boot` | Maven | From 3.0.0 to 4.0.4 | None |
| `com.github.ulisesbocchio:jasypt-spring-boot-starter` | Maven | From 3.0.0 to 4.0.4 | None |
| `com.github.ulisesbocchio:jasypt-spring-boot-starter` | Maven | From 3.0.0 to 4.0.4 | None |

## How do I fix CVE-2026-9370?

No fix has been published for CVE-2026-9370 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9370 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9370 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9370 and fix it if it is affected.

What it is: CVE-2026-9370 is a medium-severity vulnerability in ulisesbocchio jasypt-spring-boot, published on 24 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9370 exists.

Affected packages and fixed versions:
- com.github.ulisesbocchio:jasypt-spring-boot (Maven): affected from 3.0.0 up to 4.0.4; no fix listed
- com.github.ulisesbocchio:jasypt-spring-boot (Maven): affected from 3.0.0 up to 4.0.4; no fix listed
- com.github.ulisesbocchio:jasypt-spring-boot-starter (Maven): affected from 3.0.0 up to 4.0.4; no fix listed
- com.github.ulisesbocchio:jasypt-spring-boot-starter (Maven): affected from 3.0.0 up to 4.0.4; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9370/ (Markdown: https://insights.sbomify.com/CVE-2026-9370/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9370
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9370
- OSV: https://osv.dev/vulnerability/CVE-2026-9370

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9370/
Summaries are generated and may contain mistakes; the official description above is the record.