Sourced from ch.qos.logback:logback-classic'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
•
PropertiesConfiguratorModelHandlernow registers properties file URLs to theConfigurationWatchListwhen 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 bothclassandconverterClassattributes 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.•
HardenedModelInputStreamwill 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
SSLSocketAppendernow 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,
ViewStatusMessagesServletBasenow 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.
e62272a
prepare release 1.5.341e9e926
add resolveProxyClassRejectsDynamicProxies unit test2de5cbe
added StackTraceElementProxyTest, minor edits to AGENTS.md0e9b927
in case StackTraceElement is null use a substitute, fixing
issues/1040f7a0654
prevent resolveProxyClass bypass249b81f
docs are no longer distributed1c3b26a
start work on 1.5.34-SNAPSHOT124e8b4
prepare release 1.5.33d8fd6f2
escapeTags in message field when printing status messages95edbeb
hostnameVerification default to true in SSLParametersConfiguration,
SSL.DEFAU...