Skip to content

fix(deps): update dependency ch.qos.logback:logback-core to v1.5.25 [security]#732

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/maven-ch.qos.logback-logback-core-vulnerability
Open

fix(deps): update dependency ch.qos.logback:logback-core to v1.5.25 [security]#732
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/maven-ch.qos.logback-logback-core-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 20, 2026

This PR contains the following updates:

Package Change Age Confidence
ch.qos.logback:logback-core (source, changelog) 1.5.201.5.25 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Logback allows an attacker to instantiate classes already present on the class path

CVE-2026-1225 / GHSA-qqpg-mvqg-649v

More information

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.

Severity

  • CVSS Score: 1.8 / 10 (Low)
  • Vector String: CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Logback allows an attacker to instantiate classes already present on the class path

CVE-2026-1225 / GHSA-qqpg-mvqg-649v

More information

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.

Severity

  • CVSS Score: 1.8 / 10 (Low)
  • Vector String: CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot requested review from IldarMinaev and asatt as code owners May 20, 2026 11:42
@renovate renovate Bot added the dependencies Pull requests that update a dependency file label May 20, 2026
@renovate renovate Bot requested a review from vlsi as a code owner May 20, 2026 11:42
@renovate renovate Bot force-pushed the renovate/maven-ch.qos.logback-logback-core-vulnerability branch 18 times, most recently from 32ef6b2 to a83c751 Compare May 26, 2026 00:42
@renovate renovate Bot force-pushed the renovate/maven-ch.qos.logback-logback-core-vulnerability branch from a83c751 to efd0bd0 Compare May 26, 2026 05:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants