Skip to content

Update dependency ch.qos.logback:logback-core to v1.5.34 [SECURITY] - #52

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

Update dependency ch.qos.logback:logback-core to v1.5.34 [SECURITY]#52
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/maven-ch.qos.logback-logback-core-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Oct 22, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

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

Warning

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


QOS.CH logback-core is vulnerable to Arbitrary Code Execution through file processing

CVE-2025-11226 / GHSA-25qh-j22f-pwp8

More information

Details

QOS.CH logback-core versions up to 1.5.18 contain an ACE vulnerability in conditional configuration file processing in Java applications. This vulnerability allows an attacker to execute arbitrary code by compromising an existing logback configuration file or by injecting a malicious environment variable before program execution.

A successful attack requires the Janino library and Spring Framework to be present on the user's class path. Additionally, the attacker must have write access to a configuration file. Alternatively, the attacker could inject a malicious environment variable pointing to a malicious configuration file. In both cases, the attack requires existing privileges.

Severity

  • CVSS Score: 5.9 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:P/VC:H/VI:L/VA:L/SC:H/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 the GitHub Advisory Database (CC-BY 4.0).


QOS.CH Sarl logback logback-core has a deserialization of untrusted data vulnerability

CVE-2026-9828 / GHSA-p47f-322f-whfh

More information

Details

Deserialization of untrusted data vulnerability in QOS.CH Sarl logback logback-core (HardenedObjectInputStream (logback-core) modules) allows Object Injection albeit heavily restricted.

More precisely, an attacker able to influence serialized data sent to SimpleSocketServer or SimpleSSLSocketServer can instantiate objects from classes in the java.lang and java.util packages that are not explicitly blocked.

Although deserialization is heavily restricted by HardenedObjectInputStream and no practical way to achieve remote code execution or significant privilege escalation has been identified, this issue constitutes a bypass of the intended security restrictions.

This issue affects logback: through 1.5.32 inclusive.

Severity

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

References

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


Logback vulnerable to Object Injection through HardenedObjectInputStream modules

CVE-2026-10532 / GHSA-jhq6-gfmj-v8fx

More information

Details

Deserialization of untrusted data vulnerability in QOS.CH Sarl logback logback-core (HardenedObjectInputStream (logback-core) modules) allows Object Injection, albeit heavily restricted.

More precisely, an attacker able to influence serialized data sent to SimpleSocketServer or SimpleSSLSocketServer can instantiate Proxy objects.

Although deserialization is heavily restricted by HardenedObjectInputStream and no practical way to achieve remote code execution or significant privilege escalation has been identified, this issue constitutes a bypass of the intended security restrictions.

This issue affects logback: through 1.5.33 inclusive.

Severity

  • CVSS Score: 2.9 / 10 (Low)
  • Vector String: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:P/RE:M/U:Green

References

This data is provided by 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: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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 force-pushed the renovate/maven-ch.qos.logback-logback-core-vulnerability branch from 11ef8fa to 318fdda Compare January 22, 2026 20:39
@renovate renovate Bot changed the title Update dependency ch.qos.logback:logback-core to v1.5.19 [SECURITY] Update dependency ch.qos.logback:logback-core to v1.5.25 [SECURITY] Jan 22, 2026
@renovate renovate Bot changed the title Update dependency ch.qos.logback:logback-core to v1.5.25 [SECURITY] Update dependency ch.qos.logback:logback-core to v1.5.25 [SECURITY] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate
renovate Bot deleted the renovate/maven-ch.qos.logback-logback-core-vulnerability branch March 27, 2026 01:43
@renovate renovate Bot changed the title Update dependency ch.qos.logback:logback-core to v1.5.25 [SECURITY] - autoclosed Update dependency ch.qos.logback:logback-core to v1.5.25 [SECURITY] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate
renovate Bot force-pushed the renovate/maven-ch.qos.logback-logback-core-vulnerability branch 2 times, most recently from 318fdda to d463ddf Compare March 30, 2026 22:08
@renovate
renovate Bot force-pushed the renovate/maven-ch.qos.logback-logback-core-vulnerability branch from d463ddf to ab1ee90 Compare July 6, 2026 02:34
@renovate renovate Bot changed the title Update dependency ch.qos.logback:logback-core to v1.5.25 [SECURITY] Update dependency ch.qos.logback:logback-core to v1.5.33 [SECURITY] Jul 6, 2026
@renovate
renovate Bot force-pushed the renovate/maven-ch.qos.logback-logback-core-vulnerability branch from ab1ee90 to 76ecc74 Compare July 16, 2026 04:02
@renovate renovate Bot changed the title Update dependency ch.qos.logback:logback-core to v1.5.33 [SECURITY] Update dependency ch.qos.logback:logback-core to v1.5.34 [SECURITY] Jul 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants