Spring Security
86%
Total Score
healthy
Healthy: active releases and an organization-backed, maintained repository outweigh the prerelease label.
This is a prerelease milestone, so API or behavior changes may still occur even though the major version is established.
All 12 workflows were analyzed with no failed files, all 28 action references are pinned, and no untrusted checkout or script-injection paths were found. High-confidence template-injection and inherited-secret findings remain workflow hygiene concerns, while broad top-level write permissions are a mild additional concern.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-354152 spring-security-crypto is vulnerable to Use of a Broken or Risky Cryptographic Algorithm in versions 5.7.0 - 7.0.6 and 7.1.0 - 7.1.0. | 5.7.0 - 7.0.67.1.0 - 7.1.0 | Medium |
AIKIDO-2025-10171 spring-security-crypto is vulnerable to Improper Authentication in versions 0.0.0 - 6.3.7 and 6.4.0 - 6.4.3. | 0.0.0 - 6.3.76.4.0 - 6.4.3 | High |
AIKIDO-2024-10472 spring-security-crypto is vulnerable to Authorization Bypass in versions 0.0.1 - 6.2.7 and 6.3.0 - 6.3.4. | 0.0.1 - 6.2.76.3.0 - 6.3.4 | Medium |
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
org.assertj:assertj-core Version 3.27.7 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.