jasypt-spring-boot Uses a One-Way Hash without a Salt

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.9 · 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 · score source

EPSS

• CVE-2026-9370: 0.20% estimated exploitation activity in the next 30 days; percentile 10.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

26 May 2026, 13:30 UTC

Last modified by the source

30 Jun 2026, 16:30 UTC

Source last checked

26 Oct 2026, 16:53 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jgj7-c8vj-w563

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-9370

Advisory: jasypt-spring-boot Uses a One-Way Hash without a Salt
IDs: CVE-2026-9370, GHSA-jgj7-c8vj-w563
Record: https://patchnext.com/advisories/cve-2026-9370 (revision 1, source checked 26 Oct 2026, 16:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.github.ulisesbocchio:jasypt-spring-boot: affected >= 3.0.0, <= 4.0.4
- Maven com.github.ulisesbocchio:jasypt-spring-boot-starter: affected >= 3.0.0, <= 4.0.4

## Suggested inspection (read-only)
- Maven com.github.ulisesbocchio:jasypt-spring-boot: check the installed version with your package manager.
- Maven com.github.ulisesbocchio:jasypt-spring-boot-starter: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.github.ulisesbocchio:jasypt-spring-boot, com.github.ulisesbocchio:jasypt-spring-boot-starter.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jgj7-c8vj-w563 (GitHub-reviewed advisory GHSA-jgj7-c8vj-w563 lists affected ranges: Maven com.github.ulisesbocchio:jasypt-spring-boot >=3.0.0 =3.0.0 <=4.0.4)

Commands are suggestions: review each one before running it.