Skip to content

spring-boot-starter-thymeleaf-4.0.1.jar: 1 vulnerabilities (highest severity is: 5.0) #62

@mend-bolt-for-github

Description

@mend-bolt-for-github
Vulnerable Library - spring-boot-starter-thymeleaf-4.0.1.jar

Path to dependency file: /build.gradle.kts

Path to vulnerable library: /tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/ch.qos.logback/logback-core/1.5.22/7c3ee4420b36bd499fa4f9f18a81d54a64fe0218/logback-core-1.5.22.jar

Found in HEAD commit: ddc0cf112b0a41d5508a5fc8bae1c353f3f9ff7e

Vulnerabilities

Vulnerability Severity CVSS Dependency Type Fixed in (spring-boot-starter-thymeleaf version) Remediation Possible**
CVE-2026-1225 Medium 5.0 logback-core-1.5.22.jar Transitive N/A*

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2026-1225

Vulnerable Library - logback-core-1.5.22.jar

logback-core module

Library home page: http://logback.qos.ch

Path to dependency file: /build.gradle.kts

Path to vulnerable library: /tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/ch.qos.logback/logback-core/1.5.22/7c3ee4420b36bd499fa4f9f18a81d54a64fe0218/logback-core-1.5.22.jar

Dependency Hierarchy:

  • spring-boot-starter-thymeleaf-4.0.1.jar (Root Library)
    • spring-boot-starter-4.0.1.jar
      • spring-boot-starter-logging-4.0.1.jar
        • logback-classic-1.5.22.jar
          • logback-core-1.5.22.jar (Vulnerable Library)

Found in HEAD commit: ddc0cf112b0a41d5508a5fc8bae1c353f3f9ff7e

Found in base branch: master

Vulnerability Details

ACE vulnerability in configuration file processing by QOS.CH logback-core up to and including version 1.5.24 in Java applications, allows an attacker to instantiate classes already present on the class path by compromising an existing logback configuration file.
The instantiation of a potentially malicious Java class requires that said class is present on the user's class-path. In addition, the attacker must have write access to a
configuration file. However, after successful instantiation, the instance is very likely to be discarded with no further ado.

Publish Date: 2026-01-22

URL: CVE-2026-1225

CVSS 3 Score Details (5.0)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Local
    • Attack Complexity: High
    • Privileges Required: High
    • User Interaction: None
    • Scope: Changed
  • Impact Metrics:
    • Confidentiality Impact: Low
    • Integrity Impact: Low
    • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-qqpg-mvqg-649v

Release Date: 2026-01-22

Fix Resolution: ch.qos.logback:logback-core:1.5.25

Step up your Open Source Security Game with Mend here

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions