Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-jgj7-c8vj-w563

LOW

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

Also known asCVE-2026-9370
Published
May 26, 2026
Updated
Jun 30, 2026
Affected
2 pkgs
Patched
None yet
Exploits
None indexed

Blast Radius

2 pkgs affected
com.github.ulisesbocchio:jasypt-spring-bootcom.github.ulisesbocchio:jasypt-spring-boot-starter

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

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.

Affected Packages

2 total
EcosystemPackageVulnerable rangeFix
Mavencom.github.ulisesbocchio:jasypt-spring-boot3.0.0No fix
Mavencom.github.ulisesbocchio:jasypt-spring-boot-starter3.0.0No fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.github.ulisesbocchio:jasypt-spring-boot. 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.

  2. Remediation status

    No patched version of com.github.ulisesbocchio:jasypt-spring-boot has shipped for GHSA-jgj7-c8vj-w563 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-jgj7-c8vj-w563 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-jgj7-c8vj-w563. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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
O3 Security · Impact-Aware SCA

Is GHSA-jgj7-c8vj-w563 in your dependencies?

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