SpringBootDemo 1.0.0Application64 components
Recommended remediation deadlines
We recommend preparing a remediation plan or risk justification.
A finding is a match between a component's name and version and a vulnerability database; whether this product uses the vulnerable code is not checked, so some findings may not apply. A source scan also leaves out test, example and sample folders by default.
| Severity | CVE | Package | Installed | Fixed | Deadline |
|---|---|---|---|---|---|
| Critical | CVE-2025-24813 | org. | 10.1.16 | 11.0.3, 10.1.35, 9.0.99 | within 7 days |
| Critical | CVE-2026-41293 | org. | 10.1.16 | 9.0.118, 10.1.55, 11.0.22 | within 7 days |
| Critical | CVE-2026-43512 | org. | 10.1.16 | 9.0.118, 10.1.55, 11.0.22 | within 7 days |
| Critical | CVE-2026-43515 | org. | 10.1.16 | 9.0.118, 10.1.55, 11.0.22 | within 7 days |
| Critical | CVE-2026-55276 | org. | 10.1.16 | 11.0.23, 10.1.56, 9.0.119 | within 7 days |
| Critical | CVE-2026-65182 | org. | 10.1.16 | 11.0.25, 10.1.58, 9.0.121 | within 7 days |
| Critical | CVE-2026-65905 | org. | 10.1.16 | 11.0.25, 10.1.58, 9.0.121 | within 7 days |
| Critical | CVE-2026-68525 | org. | 10.1.16 | 11.0.25, 10.1.58, 9.0.121 | within 7 days |
| Critical | CVE-2026-47884 | org. | 6.1.1 | 7.0.9 | within 7 days |
| High | CVE-2023-6378 | ch. | 1.4.11 | 1.3.12, 1.4.12, 1.2.13 | within 30 days |
| High | CVE-2023-6378 | ch. | 1.4.11 | 1.3.12, 1.4.12, 1.2.13 | within 30 days |
| High | CVE-2026-68494 | com. | 2.16.0 | 2.18.8, 2.21.4 | within 30 days |
| High | CVE-2026-89425 | com. | 2.16.0 | 2.21.7, 2.22.3, 2.18.11 | within 30 days |
| High | CVE-2026-54512 | com. | 2.16.0 | 2.18.8, 3.1.4, 2.21.4 | within 30 days |
| High | CVE-2026-54513 | com. | 2.16.0 | 2.18.8, 2.21.4, 3.1.4 | within 30 days |
| High | CVE-2026-68497 | com. | 2.16.0 | 2.18.10, 2.21.6, 2.22.2 | within 30 days |
| High | CVE-2026-91776 | com. | 2.16.0 | 2.18.11, 2.21.7, 2.22.3 | within 30 days |
| High | CVE-2026-91777 | com. | 2.16.0 | 2.21.7, 2.18.11, 2.22.3 | within 30 days |
| High | CVE-2024-34750 | org. | 10.1.16 | 11.0.0-M21, 10.1.25, 9.0.90 | within 30 days |
| High | CVE-2024-38286 | org. | 10.1.16 | 11.0.0-M21, 10.1.25, 9.0.90 | within 30 days |
| High | CVE-2024-50379 | org. | 10.1.16 | 11.0.2, 10.1.34, 9.0.98 | within 30 days |
| High | CVE-2024-56337 | org. | 10.1.16 | 11.0.2, 10.1.34, 9.0.98 | within 30 days |
| High | CVE-2025-48988 | org. | 10.1.16 | 11.0.8, 10.1.42, 9.0.106 | within 30 days |
| High | CVE-2025-48989 | org. | 10.1.16 | 11.0.10, 10.1.44, 9.0.108 | within 30 days |
| High | CVE-2025-52520 | org. | 10.1.16 | 11.0.9, 10.1.43, 9.0.107 | within 30 days |
| High | CVE-2025-53506 | org. | 10.1.16 | 9.0.107, 10.1.43, 11.0.9 | within 30 days |
| High | CVE-2025-55752 | org. | 10.1.16 | 11.0.11, 10.1.45, 9.0.109 | within 30 days |
| High | CVE-2026-24734 | org. | 10.1.16 | 11.0.18, 10.1.52, 9.0.115 | within 30 days |
| High | CVE-2026-24880 | org. | 10.1.16 | 9.0.116, 10.1.52, 11.0.20 | within 30 days |
| High | CVE-2026-34483 | org. | 10.1.16 | 9.0.116, 10.1.54, 11.0.21 | within 30 days |
| High | CVE-2026-34487 | org. | 10.1.16 | 9.0.117, 10.1.54, 11.0.21 | within 30 days |
| High | CVE-2026-41284 | org. | 10.1.16 | 9.0.118, 10.1.55, 11.0.22 | within 30 days |
| High | CVE-2026-42498 | org. | 10.1.16 | 9.0.118, 10.1.55, 11.0.22 | within 30 days |
| High | CVE-2026-43513 | org. | 10.1.16 | 9.0.118, 10.1.55, 11.0.22 | within 30 days |
| High | CVE-2026-53404 | org. | 10.1.16 | 11.0.23, 10.1.56, 9.0.119 | within 30 days |
| High | CVE-2026-55957 | org. | 10.1.16 | 11.0.5, 10.1.37, 9.0.101 | within 30 days |
| High | CVE-2025-22235 | org. | 3.2.0 | 3.3.11, 3.4.5 | within 30 days |
| High | CVE-2025-41249 | org. | 6.1.1 | 6.2.11 | within 30 days |
| High | CVE-2026-41850 | org. | 6.1.1 | 7.0.8, 6.2.19 | within 30 days |
| High | CVE-2024-22243 | org. | 6.1.1 | 6.1.4, 6.0.17, 5.3.32 | within 30 days |
| High | CVE-2024-22259 | org. | 6.1.1 | 6.1.5, 6.0.18, 5.3.33 | within 30 days |
| High | CVE-2024-22262 | org. | 6.1.1 | 5.3.34, 6.0.19, 6.1.6 | within 30 days |
| High | CVE-2024-38816 | org. | 6.1.1 | 6.1.13 | within 30 days |
| High | CVE-2024-38819 | org. | 6.1.1 | 6.1.14 | within 30 days |
| High | CVE-2026-41842 | org. | 6.1.1 | 7.0.8, 6.2.19 | within 30 days |
| High | CVE-2026-41845 | org. | 6.1.1 | 7.0.8, 6.2.19 | within 30 days |
| Medium | CVE-2024-12798 | ch. | 1.4.11 | 1.5.13, 1.3.15 | Per policy |
| Medium | CVE-2025-11226 | ch. | 1.4.11 | 1.5.19, 1.3.16 | Per policy |
| Medium | CVE-2026-18401 | com. | 2.16.0 | 2.21.1, 2.18.6 | Per policy |
| Medium | CVE-2026-19032 | com. | 2.16.0 | 2.18.10, 2.21.6, 2.22.2 | Per policy |
| Medium | CVE-2026-54514 | com. | 2.16.0 | 2.18.8, 2.21.4 | Per policy |
| Medium | CVE-2026-54515 | com. | 2.16.0 | 3.1.4, 2.18.9, 2.21.5, 2.22.1 | Per policy |
| Medium | CVE-2026-59888 | com. | 2.16.0 | 2.18.8, 2.21.4 | Per policy |
| Medium | CVE-2026-59889 | com. | 2.16.0 | 2.21.5, 2.18.9, 2.22.1 | Per policy |
| Medium | CVE-2026-77310 | com. | 2.16.0 | 2.18.9, 2.21.5, 2.22.1 | Per policy |
| Medium | CVE-2026-83557 | com. | 2.16.0 | 2.18.10, 2.21.6, 2.22.2 | Per policy |
| Medium | CVE-2025-48924 | org. | 3.14.0 | 3.18.0 | Per policy |
| Medium | CVE-2026-49844 | org. | 2.21.1 | 2.25.5, 2.26.1 | Per policy |
| Medium | CVE-2024-24549 | org. | 10.1.16 | 8.5.99, 9.0.86, 10.1.19, 11.0.0-M17 | Per policy |
| Medium | CVE-2025-31650 | org. | 10.1.16 | 9.0.104, 10.1.40, 11.0.6 | Per policy |
| Medium | CVE-2025-49124 | org. | 10.1.16 | 11.0.8, 10.1.42, 9.0.106 | Per policy |
| Medium | CVE-2025-49125 | org. | 10.1.16 | 11.0.8, 10.1.42, 9.0.106 | Per policy |
| Medium | CVE-2025-55668 | org. | 10.1.16 | 11.0.8, 10.1.42, 9.0.106 | Per policy |
| Medium | CVE-2025-66614 | org. | 10.1.16 | 11.0.15, 10.1.50, 9.0.113 | Per policy |
| Medium | CVE-2026-25854 | org. | 10.1.16 | 9.0.116, 10.1.53, 11.0.20 | Per policy |
| Medium | CVE-2026-55956 | org. | 10.1.16 | 11.0.23, 10.1.56, 9.0.119 | Per policy |
| Medium | CVE-2024-23672 | org. | 10.1.16 | 11.0.0-M17, 10.1.19, 9.0.86, 8.5.99 | Per policy |
| Medium | CVE-2026-41711 | org. | 3.2.0 | 4.0.6, 3.5.12 | Per policy |
| Medium | CVE-2026-41721 | org. | 3.2.0 | 4.0.6, 3.5.12 | Per policy |
| Medium | CVE-2024-38820 | org. | 6.1.1 | 6.1.14 | Per policy |
| Medium | CVE-2026-41851 | org. | 6.1.1 | 7.0.8, 6.2.19 | Per policy |
| Medium | CVE-2024-38809 | org. | 6.1.1 | 5.3.38, 6.0.23, 6.1.12 | Per policy |
| Medium | CVE-2024-38820 | org. | 6.1.1 | 6.1.14 | Per policy |
| Medium | CVE-2025-41234 | org. | 6.1.1 | 6.2.8, 6.1.21 | Per policy |
| Medium | CVE-2025-41242 | org. | 6.1.1 | 6.2.10 | Per policy |
| Medium | CVE-2026-22737 | org. | 6.1.1 | 7.0.6, 6.2.17 | Per policy |
| Medium | CVE-2026-22745 | org. | 6.1.1 | 7.0.7, 6.2.18 | Per policy |
| Medium | CVE-2026-41841 | org. | 6.1.1 | 7.0.8, 6.2.19 | Per policy |
| Medium | CVE-2026-41843 | org. | 6.1.1 | 7.0.8, 6.2.19 | Per policy |
| Medium | CVE-2026-41844 | org. | 6.1.1 | 7.0.8, 6.2.19 | Per policy |
| Medium | CVE-2026-41846 | org. | 6.1.1 | 7.0.8, 6.2.19 | Per policy |
| Medium | CVE-2026-41853 | org. | 6.1.1 | 7.0.8, 6.2.19 | Per policy |
| Low | CVE-2024-12801 | ch. | 1.4.11 | 1.5.13, 1.3.15 | Per policy |
| Low | CVE-2026-10532 | ch. | 1.4.11 | 1.5.34 | Per policy |
| Low | CVE-2026-1225 | ch. | 1.4.11 | 1.5.25 | Per policy |
| Low | CVE-2026-9828 | ch. | 1.4.11 | 1.5.33 | Per policy |
| Low | CVE-2025-31651 | org. | 10.1.16 | 9.0.104, 10.1.40, 11.0.6 | Per policy |
| Low | CVE-2025-46701 | org. | 10.1.16 | 9.0.105, 10.1.41, 11.0.7 | Per policy |
| Low | CVE-2025-55754 | org. | 10.1.16 | 11.0.11, 10.1.45, 9.0.109 | Per policy |
| Low | CVE-2025-61795 | org. | 10.1.16 | 11.0.12, 10.1.47, 9.0.110 | Per policy |
| Low | CVE-2026-43514 | org. | 10.1.16 | 9.0.118, 10.1.55, 11.0.22 | Per policy |
| Low | CVE-2025-22233 | org. | 6.1.1 | 6.2.7, 6.1.20 | Per policy |
| Low | CVE-2026-41848 | org. | 6.1.1 | 7.0.8, 6.2.19 | Per policy |
| Low | CVE-2026-41852 | org. | 6.1.1 | 7.0.8, 6.2.19 | Per policy |
| Low | CVE-2026-22735 | org. | 6.1.1 | 7.0.6, 6.2.17 | Per policy |
| Low | CVE-2026-22741 | org. | 6.1.1 | 7.0.7, 6.2.18 | Per policy |
Distinct licenses identified: 10 (see the NOTICE artifact for details).
Licenses are what each package declares. A declaration can be missing or wrong, and this is not a legal determination.
Each component is also recorded in the SBOM with a bomlens:licenseClass property. An unrecognized license is left uncategorized rather than assumed permissive.
Dependencies checked against the declared outbound license. Advisory only — it surfaces combinations that need a person to look, and makes no legal determination.
Conflicts with the outbound license (Apache-2.0)
8 Incompatible 0 Conditional 8 Unknown 0spring-boot-starter-web 3.2.0 (76 finding(s)), jackson-databind 2.16.0 (15 finding(s)), spring-boot-starter-data-jpa 3.2.0 (2 finding(s)).