CVE-2026-9370

LOWPre-NVD 3.73.7—
EchelonGraph scoreMEDIUM confidence

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-05-26. the CNA's CVSS baseline 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vuldb, epss, ghsa
Elevated
3.7
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.7Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
3.7
EG Score
3.7(medium)
EPSS
10.2%
KEV
Not listed

Published

May 24, 2026

Last Modified

May 29, 2026

References (6)

Vendor Advisories for CVE-2026-9370(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFixed inDependents
com.github.ulisesbocchio:jasypt-spring-boot3.0.0 ... 4.0.4 (8 versions)——
com.github.ulisesbocchio:jasypt-spring-boot-starter3.0.0 ... 4.0.4 (8 versions)——

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-09 19:10 UTCEPSS rescore
  2. 2026-07-08 15:16 UTCEPSS rescore
  3. 2026-07-07 13:46 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 02:31 UTCEPSS rescore
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-01 15:07 UTCEPSS rescore
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 13:30 UTCEG score recompute
  14. 2026-06-28 13:30 UTCGHSA enrichment
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-27 03:08 UTCEPSS rescore
  17. 2026-06-25 13:50 UTCEPSS rescore
  18. 2026-06-25 13:48 UTCEG score recompute
  19. 2026-06-25 13:48 UTCGHSA enrichment
  20. 2026-06-24 14:05 UTCEPSS rescore
  21. 2026-06-23 21:33 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 01:59 UTCEPSS rescore
  25. 2026-06-19 19:26 UTCEPSS rescore
Show 39 more
  1. 2026-06-18 17:52 UTCEPSS rescore
  2. 2026-06-17 17:53 UTCEPSS rescore
  3. 2026-06-16 17:53 UTCEPSS rescore
  4. 2026-06-16 01:03 UTCEG score recompute
  5. 2026-06-16 01:03 UTCGHSA enrichment
  6. 2026-06-15 17:49 UTCEPSS rescore
  7. 2026-06-15 17:49 UTCEPSS rescore
  8. 2026-06-14 23:18 UTCEPSS rescore
  9. 2026-06-13 23:00 UTCEPSS rescore
  10. 2026-06-13 01:18 UTCEG score recompute
  11. 2026-06-13 01:18 UTCGHSA enrichment
  12. 2026-06-12 23:12 UTCEPSS rescore
  13. 2026-06-12 23:12 UTCEPSS rescore
  14. 2026-06-11 14:00 UTCEPSS rescore
  15. 2026-06-10 22:19 UTCEPSS rescore
  16. 2026-06-10 13:22 UTCEPSS rescore
  17. 2026-06-10 01:32 UTCEG score recompute
  18. 2026-06-10 01:32 UTCGHSA enrichment
  19. 2026-06-08 14:17 UTCEPSS rescore
  20. 2026-06-07 15:25 UTCEPSS rescore
  21. 2026-06-07 01:50 UTCEG score recompute
  22. 2026-06-07 01:50 UTCGHSA enrichment
  23. 2026-06-06 13:47 UTCEPSS rescore
  24. 2026-06-05 22:47 UTCEPSS rescore
  25. 2026-06-04 13:12 UTCEPSS rescore
  26. 2026-06-04 02:08 UTCEG score recompute
  27. 2026-06-04 02:08 UTCGHSA enrichment
  28. 2026-06-02 20:13 UTCEPSS rescore
  29. 2026-06-01 13:52 UTCEPSS rescore
  30. 2026-06-01 02:26 UTCEG score recompute
  31. 2026-06-01 02:26 UTCGHSA enrichment
  32. 2026-05-31 22:30 UTCEPSS rescore
  33. 2026-05-31 00:16 UTCEPSS rescore
  34. 2026-05-29 13:44 UTCEPSS rescore
  35. 2026-05-28 13:44 UTCEPSS rescore
  36. 2026-05-27 13:40 UTCEPSS rescore
  37. 2026-05-26 13:44 UTCEPSS rescore
  38. 2026-05-26 07:18 UTCEPSS rescore
  39. 2026-05-24 09:51 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-9370?
CVE-2026-9370 is a low vulnerability published on May 24, 2026. 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…
When was CVE-2026-9370 disclosed?
CVE-2026-9370 was first published in the National Vulnerability Database on May 24, 2026, with the most recent update on May 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9370 actively exploited?
CVE-2026-9370 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 10.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9370?
CVE-2026-9370 has a CVSS v4.0 base score of 3.7 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-9370?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9370, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-9370

Explore →

Is Your Infrastructure Affected by CVE-2026-9370?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs