Bump ch.qos.logback:logback-core from 1.3.15 to 1.5.34 in /java

[dependabot]

Bumps ch.qos.logback:logback-core from 1.3.15 to 1.5.34.

Release notes

Sourced from ch.qos.logback:logback-core's releases.

Logback 1.5.34

2026-06-01 Release of logback version 1.5.34

• In case certain StackTraceElement values returned by the Throwable.getStackTrace method are null, StackTraceElementProxy substitutes a dummy instance instead of throwing an IllegalArgumentException. This resolves [issues #1040](qos-ch/logback#1040), reported by Naotsugu Kobayashi.

• HardenedObjectInputStream will now throw an InvalidClassException during deserialization attempts of Proxy classes. This change addresses potential deserialization whitelist bypass vulnerability reported by York Shen and registered as CVE-2026-10532.

• A bitwise identical binary of this version can be reproduced by building from source code at commit e62272ac152469aec1ede056c3c7d0d7314e7bfe associated with the tag v_1.5.34. This release was built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.

Logback 1.5.33

2026-05-27 Release of logback version 1.5.33

• PropertiesConfiguratorModelHandler now registers properties file URLs to the ConfigurationWatchList when scan is enabled (via local scan="true" attribute or top-level configuration scan), ensuring changes are detected and reconfiguration occurs. This problem was reported in issues/1034.

• When processing <conversionRule> elements and both class and converterClass attributes are specified, silently use the class attribute without issuing a warning. However, if the attribute values differ, a warning will be issued. This change was requested in issues/1031.

• HardenedModelInputStream will no longer accept to deserialize all classes located under the "java.lang" and "java.util" packages but a limited number of explicitly authorized classes in those packages. This potential deserialization whitelist bypass vulnerability was reported by York Shen and registered as CVE-2026-9828.

• SSL parameters for SSLSocketAppender now enable hostname verification by default. Moreover, the default protocol is now "TLSv1.2". This potential vulnerability was reported by York Shen.

• When printing the status message field, ViewStatusMessagesServletBase now escapes special characters such as "&" as character entities. This potential vulnerability was reported by York Shen.

• A bit-wise identical binary of this version can be reproduced by building from source code at commit 124e8b49b55ac34d08743a0646bd463410192647 associated with the tag v_1.5.33. Release built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.

Logback 1.5.32

2026-02-16 Release of logback version 1.5.32

• In DefaultProcessor, fixed incorrect check for dependencies contained within a parent model. Previous only the direct children were scanned. This fixes logback-access/issues/34.

• A bit-wise identical binary of this version can be reproduced by building from source code at commit e807335a67535b4eacce94e942c0bcb649665d93 associated with the tag v_1.5.32. Release built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.

Logback 1.5.31

2026-02-14 Release of logback version 1.5.31

• Fixed missing META-INF/services directory in logback-classic.jar. This issue rendered logback-classic version 1.5.30 unusable with SLF4J.

• A bit-wise identical binary of this version can be reproduced by building from source code at commit 168e42f9f9a18a3ffdf31eb2bfe80a71e33ecd8b associated with the tag v_1.5.31. Release built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.

Logback 1.5.30

2026-02-14 Release of logback version 1.5.30

• In this version, logback-classic.jar was missing the META-INF/services directory, making it unusable with SLF4J. Version 1.5.31 (released later on the same day) fixes this issue.

• Fix scanning issue when an included file becomes available at a later time. This problem was reported in issues/1021 by Sergey Nazarov.

• Standardized code for version checking across modules.

• A bit-wise identical binary of this version can be reproduced by building from source code at commit 44164f10ca3fb44ce0e68519f13564b87e3aca61 associated with the tag v_1.5.30. Release built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.

Logback 1.5.29

... (truncated)

Commits

• e62272a prepare release 1.5.34
• 1e9e926 add resolveProxyClassRejectsDynamicProxies unit test
• 2de5cbe added StackTraceElementProxyTest, minor edits to AGENTS.md
• 0e9b927 in case StackTraceElement is null use a substitute, fixing issues/1040
• f7a0654 prevent resolveProxyClass bypass
• 249b81f docs are no longer distributed
• 1c3b26a start work on 1.5.34-SNAPSHOT
• 124e8b4 prepare release 1.5.33
• d8fd6f2 escapeTags in message field when printing status messages
• 95edbeb hostnameVerification default to true in SSLParametersConfiguration, SSL.DEFAU...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[RockteMQ-AI]

Review by github-manager-bot

Summary

Dependabot version bump: ch.qos.logback:logback-core from 1.3.15 → 1.5.34 in the Java client SDK module. Single-line change in java/pom.xml.

Analysis

Security fixes included (good reasons to upgrade):

• CVE-2026-10532 — HardenedObjectInputStream deserialization whitelist bypass
• CVE-2026-9828 — Deserialization whitelist bypass via java.lang/java.util packages
• SSL hostname verification fix for SSLSocketAppender

Compatibility check:

• Logback 1.5.x requires SLF4J 2.x — project already uses slf4j.version=2.0.13 ✅
• Logback 1.3.x → 1.5.x is a minor version jump within the same SLF4J 2.x compatible branch — safe
• Logback is used for test/example logging in the client SDK, not in production runtime path — low blast radius

Findings

• [Info] java/pom.xml:57 — Version bump is straightforward. The security fixes (especially the deserialization CVEs) make this a worthwhile upgrade.

Verdict

LGTM. Low-risk dependency update with meaningful security fixes.

---

Automated review by github-manager-bot

[RockteMQ-AI]

Review by github-manager-bot

PR: Bump ch.qos.logback:logback-core from 1.3.15 to 1.5.34 in /java
Verdict: ✅ Approved

Summary

Dependabot version bump of logback-core from 1.3.15 to 1.5.34 in the Java client module. Single-line change in java/pom.xml.

Findings

• [Info] java/pom.xml:57 — This is a significant version jump (1.3.x → 1.5.x). Logback 1.4+ migrated to Jakarta EE 9+ (jakarta.* namespace). Since this is a client SDK and logback is typically used only for test/runtime logging (not exposed as a public API), the impact should be minimal.
• [Info] SLF4J compatibility: The project uses slf4j.version=2.0.13 which is compatible with logback 1.5.x (both target SLF4J 2.x API). ✅
• [Info] No code changes required — logback 1.5.x maintains backward compatibility with the public logging API used by application code.

Suggestions

• Consider verifying that integration tests pass with the new logback version, especially if any test fixtures rely on specific log output formats.
• If the project uses logback-classic elsewhere, ensure it is also updated to match logback-core 1.5.34 (version mismatch between classic and core can cause runtime issues).

---

Automated review by github-manager-bot