CVE-2026-9370Public exploit

Secret recovery via deterministic password-derived keys

Published May 24, 2026 · Updated May 24, 2026

Cryptographic weakness in jasypt-spring-boot 3.0.0 through 4.0.4 allows attackers to recover secrets from captured ciphertext. SimpleGCMConfig.getSecretKeySaltGenerator returns ZeroSaltGenerator when the GCM salt is unset, causing PBKDF2 to derive identical AES keys from identical passwords. Exploitation requires GCM password mode, an omitted salt, access to ciphertext, and a guessable or reused master password; the consequence is offline secret recovery and cross-deployment key reuse.

CVSS severity3.7
Low
EPSS probability0.20%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Cryptographic weakness in jasypt-spring-boot 3.0.0 through 4.0.4 allows attackers to recover secrets from captured ciphertext. SimpleGCMConfig.getSecretKeySaltGenerator returns ZeroSaltGenerator when the GCM salt is unset, causing PBKDF2 to derive identical AES keys from identical passwords. Exploitation requires GCM password mode, an omitted salt, access to ciphertext, and a guessable or reused master password; the consequence is offline secret recovery and cross-deployment key reuse.

The record

CVE
CVE-2026-9370
Published
May 24, 2026
Updated
May 24, 2026
Vendor
Ulises Bocchio
Product
jasypt-spring-boot
Classifications
CWE-760, CWE-759, T1110.002
Attack vector
local
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 24, 2026CVE publishedPublication date reported by the CVE source.
  2. May 24, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=3.0.0
  2. Affected versionversion=3.0.1
  3. Affected versionversion=3.0.2
  4. Affected versionversion=3.0.3
  5. Affected versionversion=3.0.4
  6. Affected versionversion=3.0.5
  7. Affected versionversion=4.0.0
  8. Affected versionversion=4.0.1
  9. Affected versionversion=4.0.2
  10. Affected versionversion=4.0.3
  11. Affected versionversion=4.0.4

What conditions does exploitation require?

Attack vectorlocal
Required privilegesunauthenticated

What is affected?

Ulises Bocchio · jasypt-spring-bootversion=3.0.0; version=3.0.1; version=3.0.2; version=3.0.3; version=3.0.4; version=3.0.5; version=4.0.0; version=4.0.1; version=4.0.2; version=4.0.3; version=4.0.4

Published CVSS scores

3.7VulDBCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
2.9VulDBCVSS: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
2.6VulDBAV:N/AC:H/Au:N/C:P/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-760Use of a One-Way Hash with a Predictable Salt
CWE-759Use of a One-Way Hash without a Salt
T1110.002Password Cracking

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo