Logback

Frameworks & Libraries

Logging framework for Java that implements the SLF4J API natively.

Latest 1.6.7 · by QOS.chWritten in JavaWebsiteqos-ch/logbackRSS

Release activity

Release activity — 25 releases across 23 days in the last year. Each cell is one day; darker means more releases that day. Older weeks are hidden at this screen width.
AugSepOctNov
SundayNo releases on Aug 2, 2026No releases on Aug 9, 2026No releases on Aug 16, 2026No releases on Aug 23, 2026No releases on Aug 30, 2026No releases on Sep 6, 2026No releases on Sep 13, 2026No releases on Sep 20, 2026No releases on Sep 27, 2026No releases on Oct 4, 2026No releases on Oct 11, 2026No releases on Oct 18, 20261 release on Oct 25, 2026No releases on Nov 1, 2026No releases on Nov 8, 2026No releases on Nov 15, 2026
MondayNo releases on Aug 3, 2026No releases on Aug 10, 2026No releases on Aug 17, 2026No releases on Aug 24, 2026No releases on Aug 31, 2026No releases on Sep 7, 2026No releases on Sep 14, 2026No releases on Sep 21, 2026No releases on Sep 28, 2026No releases on Oct 5, 2026No releases on Oct 12, 2026No releases on Oct 19, 2026No releases on Oct 26, 2026No releases on Nov 2, 2026No releases on Nov 9, 2026
TuesdayNo releases on Aug 4, 20261 release on Aug 11, 2026No releases on Aug 18, 2026No releases on Aug 25, 2026No releases on Sep 1, 2026No releases on Sep 8, 2026No releases on Sep 15, 2026No releases on Sep 22, 2026No releases on Sep 29, 2026No releases on Oct 6, 2026No releases on Oct 13, 2026No releases on Oct 20, 2026No releases on Oct 27, 2026No releases on Nov 3, 2026No releases on Nov 10, 2026
WednesdayNo releases on Aug 5, 2026No releases on Aug 12, 2026No releases on Aug 19, 2026No releases on Aug 26, 2026No releases on Sep 2, 2026No releases on Sep 9, 2026No releases on Sep 16, 2026No releases on Sep 23, 2026No releases on Sep 30, 2026No releases on Oct 7, 2026No releases on Oct 14, 2026No releases on Oct 21, 2026No releases on Oct 28, 2026No releases on Nov 4, 2026No releases on Nov 11, 2026
ThursdayNo releases on Aug 6, 2026No releases on Aug 13, 2026No releases on Aug 20, 2026No releases on Aug 27, 2026No releases on Sep 3, 2026No releases on Sep 10, 2026No releases on Sep 17, 20261 release on Sep 24, 2026No releases on Oct 1, 2026No releases on Oct 8, 2026No releases on Oct 15, 2026No releases on Oct 22, 2026No releases on Oct 29, 2026No releases on Nov 5, 2026No releases on Nov 12, 2026
FridayNo releases on Aug 7, 20261 release on Aug 14, 2026No releases on Aug 21, 2026No releases on Aug 28, 2026No releases on Sep 4, 2026No releases on Sep 11, 2026No releases on Sep 18, 2026No releases on Sep 25, 20261 release on Oct 2, 2026No releases on Oct 9, 2026No releases on Oct 16, 2026No releases on Oct 23, 2026No releases on Oct 30, 2026No releases on Nov 6, 2026No releases on Nov 13, 2026
SaturdayNo releases on Aug 8, 2026No releases on Aug 15, 2026No releases on Aug 22, 2026No releases on Aug 29, 2026No releases on Sep 5, 2026No releases on Sep 12, 2026No releases on Sep 19, 2026No releases on Sep 26, 2026No releases on Oct 3, 2026No releases on Oct 10, 2026No releases on Oct 17, 2026No releases on Oct 24, 2026No releases on Oct 31, 2026No releases on Nov 7, 20261 release on Nov 14, 2026

25 releases in the last year, busiest day 3

Changelog

1.6.7Latest

Logback 1.6.7

Added 7
  • New module logback-core-kryo providing KryoEncoder and KryoDecoder for encoding and decoding logging events with the Kryo 5 serialization library
  • New module logback-classic-kryo providing Kryo 5 based encoding and decoding of ILoggingEvent instances
  • KryoEncoder supports the Vanilla (stream version 0) and Custom (stream version 5, default) formats selectable through the serializerType property
  • The Custom Kryo stream format is framed so that the decoder can recover from torn or truncated writes, such as after an application crash
  • Kryo modules require Java 11 and ship with JPMS module descriptors ch.qos.logback.core.kryo and ch.qos.logback.classic.kryo
  • Added toBooleanObject(String, Boolean) method to OptionHelper
  • Added toLopsidedBooleanObject method to OptionHelper
Changed 2
  • The scan period for a propertiesConfigurator file is taken from the scanPeriod attribute of the top-level configuration element
  • With scan="false" on propertiesConfigurator and scan="true" at the top level, the properties file is no longer monitored
Fixed 2
  • The scan attribute of the propertiesConfigurator element now takes precedence over the scan attribute of the top-level configuration element in both directions, so a properties file set to scan="true" is actually monitored for changes when top-level scanning is disabled or unset
  • When several propertiesConfigurator elements with scan="true" are present without top-level scanning, all referenced files are now monitored instead of only the last one

From Logback

2026-11-14 Release of logback version 1.6.7

• The scan attribute of the <propertiesConfigurator> element, when set, now takes precedence over the scan attribute of the top-level <configuration> element, in both directions. With scan="true" and scanning disabled or unset at the top level, the properties file is now actually monitored for changes. Previously, the file was added to the watch list but no task ever polled it. The scan period is taken from the scanPeriod attribute of the top-level <configuration> element. Conversely, with scan="false" and scan="true" at the top level, the properties file is no longer monitored. Moreover, when several <propertiesConfigurator scan="true"> elements are present without top-level scanning, all the referenced files are now monitored. Previously, only the last one was.

• Two new modules, logback-core-kryo and logback-classic-kryo, encode and decode logging events with the Kryo 5 serialization library. KryoEncoder writes ILoggingEvent instances into a compact binary stream and KryoDecoder reads them back. Two stream formats are supported, selected by the serializerType property of KryoEncoder: Vanilla (stream version 0) and Custom (stream version 5, the default). The custom format is framed so that the decoder can recover from torn or truncated writes, for example after a crash of the application. Both modules require Java 11 and ship with JPMS module descriptors, namely ch.qos.logback.core.kryo and ch.qos.logback.classic.kryo. See documentation at KryoEncoder.

• Added the toBooleanObject(String, Boolean) and toLopsidedBooleanObject methods in OptionHelper.

View originalPermalink
How 1.6.7 went
1.6.6

Logback 1.6.6

Added 1
  • The stand-alone month pattern letter L is supported in date patterns
Changed 4
  • Date pattern conversion to regular expressions follows DateTimeFormatter rules instead of SimpleDateFormat rules
  • When the syslog socket cannot be connected, SyslogOutputStream falls back to an unconnected socket and SyslogAppenderBase emits a warning
  • A datagram failing with an ICMP port unreachable error on a connected socket is resent once, and a single warning is emitted if the retry also fails instead of one error per event
  • LogbackMDCAdapter stores MDC entries in a LinkedHashMap so the %X converter outputs them in insertion order
Fixed 5
  • FileNamePattern escapes regular expression metacharacters such as parentheses, brackets and plus signs in literal parts of file name patterns, so RollingFileAppender no longer fails to start on paths with unbalanced parentheses
  • SizeAndTimeBasedRollingPolicy recognizes existing archives for patterns containing parenthesized literal segments, so maxHistory and totalSizeCap remove them and rollover no longer overwrites them after a restart
  • Regular expression metacharacters in %d date patterns are escaped when converted to regular expressions
  • OutputStreamAppender stops its encoder when the appender is stopped, releasing resources and preventing heap growth on reconfiguration
  • An unmatched right curly brace during variable substitution reports an error and leaves the original value unchanged instead of silently dropping the brace and following characters
Security 2
  • LoggingEventVO rejects during deserialization throwable proxies whose cause or suppressed entries point back into the proxy graph, preventing infinite loops and stack overflows from crafted socket receiver streams
  • SyslogOutputStream connects its DatagramSocket to the syslog host instead of binding it to the wildcard address
View originalRead the notes
How 1.6.6 went
1.6.5

Logback 1.6.5

Changed 2
  • MDCBasedDiscriminator used by SiftingAppender now rejects MDC values instead of stripping characters from them, rejecting values that are empty, longer than 64 characters, contain '..', or contain any of the characters / \ $ { } [ ] ( ) | ? * + % , @
  • MDCBasedDiscriminator returns the value of its DefaultValue property when an MDC value is rejected, and emits rate-limited warnings for each rejected value
Fixed 1
  • TimeBasedRollingPolicy and SizeAndTimeBasedRollingPolicy now remove old uncompressed log files when compression is enabled, so they are no longer ignored by maxHistory and accumulating indefinitely
Deprecated 1
  • SimpleInvocationGate, deprecated in version 1.6.3, is now marked for removal; use FixedIntervalInvocationGate instead
Security 1
  • Fixed CVE-2026-104721, a vulnerability closely related to CVE-2026-19880, where MDC values could still contain relative path components, variable references, or special characters after the version 1.6.3 fix stripping slashes
View originalRead the notes
How 1.6.5 went
1.6.4

Logback 1.6.4

Added 1
  • Encoder interface has a new default method isStateful() that returns false, allowing stateful encoders to return true
Changed 4
  • OutputStreamAppender and FileAppender hold their write lock while encoding and writing for stateful encoders so concurrent appends cannot interleave
  • In prudent mode, FileAppender encodes and writes each event while holding the lock
  • TimeBasedRollingPolicy supports half-day periods, rolling over at both 00:00 and 12:00 for date patterns with the AM/PM marker such as %d{yyyy-MM-dd-a}
  • JansiConsoleAppender emits warnings explaining how to add org.jline:jansi-core when org.jline.jansi.AnsiConsole is missing, then writes to the plain console stream
Fixed 4
  • Variable substitution is applied again to the scan attribute of the configuration element, so values such as ${logback.scan.enabled:-true} are resolved
  • Variable substitution is applied to the scan attribute of propertiesConfigurator
  • Race conditions in OutputStreamAppender and FileAppender where an event could be written before the encoder header or after the footer
  • Data race on the logger count in LoggerContext that could make LoggerContext.size() return a value lower than the actual number of loggers; the counter is now an AtomicInteger
Removed 1
  • Unused class ch.qos.logback.classic.util.LogbackMDCAdapterSimple was removed; LogbackMDCAdapter remains the default MDC adapter
View originalRead the notes
How 1.6.4 went
1.6.3

Logback 1.6.3

Added 3
  • When MDC value sanitisation actually changes a value, a rate-limited warning is emitted (a small batch followed by a lull of about ten minutes)
  • JansiConsoleAppender class wraps stdout or stderr with Jansi so ANSI escape sequences render correctly on terminals that need it, notably Windows
  • BatchedFixedIntervalInvocationGate allows a short burst of invocations before applying a fixed lull
Changed 2
  • ConsoleAppender no longer closes System.out or System.err when stopped, since the process console is not treated as an exclusive resource
  • SimpleInvocationGate is renamed FixedIntervalInvocationGate
Fixed 2
  • JansiConsoleAppender pairs each AnsiConsole.systemInstall() with systemUninstall() on stop, so repeated start/stop cycles no longer leave Jansi installed or tear down streams shared with the JVM (issues/1063)
  • The JPMS module-info for logback-core now exports the ch.qos.logback.core.property package, which had been missing from the module descriptor
Deprecated 1
  • The withJansi property on ConsoleAppender is deprecated; new setups should use JansiConsoleAppender instead, while existing configurations continue to work
Security 1
  • MDCBasedDiscriminator (used by SiftingAppender) strips forward and backward slashes from MDC values before using them as discriminating keys, preventing path segments from escaping into attacker-controlled destinations (CVE-2026-19880)
View originalRead the notes
How 1.6.3 went
1.6.2

Logback 1.6.2

Added 4
  • Configuration analysis detects contradictory caller-data inclusion instructions, such as an AsyncAppender, SocketAppender or SMTPAppender with includeCallerData left at false combined with a layout or encoder pattern using caller-data converters, and emits a configuration-time warning
  • Caller-contradiction analysis can be disabled by setting the logback.skipCallerContradictionAnalysis variable to true, either as a system property or in the configuration file
  • Programmatic registration of allowed client addresses for the simple socket servers via addAllowedClientAddress(String) and setAllowedClientAddresses(Collection)
  • ThrowableProxyVOBuilder for assembling a ThrowableProxyVO field by field, with a ThrowableProxyVO.builder() entry point
Changed 3
  • SimpleSocketServer and SimpleSSLSocketServer require an explicit client IP whitelist supplied as single IPs or CIDR ranges, and an empty whitelist accepts no clients
  • Dependency analysis handlers run their postHandle method after child models have been processed, so checks depending on nested appenders see a complete picture
  • Updated several dependencies, including Angus Mail to 2.0.4 and Jetty (test) to 12.1.12
View originalRead the notes
How 1.6.2 went
1.6.1

Logback 1.6.1

Added 4
  • The optional org.jline:jansi-core artifact is declared as a dependency alongside the existing FuseSource jansi dependency
  • A preferredJansiClassName property was added for tests
  • LayoutWrappingEncoder reports an error at start() when no layout is set
  • FileCollisionAnalyser detects file collisions involving nested appenders of SiftingAppender and issues a configuration-time warning naming the appender, discriminator key, and shared target when the nested file or fileNamePattern does not reference the key
Changed 4
  • In TimeBasedRollingPolicy with the file option set, the intermediate file renamed before asynchronous compression now uses the target archive name without the compression suffix instead of a nanotime-based .tmp suffix
  • Compression strategies now delete the source file only after successful GZ, ZIP, or XZ compression and emit a warning that the original was left intact on failure
  • ConsoleAppender with withJansi now probes org.jline.jansi.AnsiConsole first and falls back to the legacy org.fusesource.jansi.AnsiConsole class
  • SyslogOutputStream and SyslogAppenderBase close() now ensures resources are closed, and writes and flushes check that underlying resources are in a valid state, falling back to no-op otherwise
Fixed 3
  • The original uncompressed log file is no longer deleted when GZ, ZIP, or XZ compression fails
  • ANSI coloring in ConsoleAppender with withJansi keeps working after Jansi moved under the JLine project
  • LayoutWrappingEncoder guards encode() against a null layout, preventing a NullPointerException on every event and silent log loss
View originalRead the notes
How 1.6.1 went
1.6.0

Logback 1.6.0

Changed 2
  • In AsyncAppenderBase, the put(ILoggingEvent) method now has the protected modifier to allow access from derived classes
  • Bumped SLF4J dependency to version 2.0.18
Removed 1
  • Removed certain deprecated variables, methods, and classes; the full list of removed members is in release_1.6.0.txt
View originalRead the notes
How 1.6.0 went
1.5.38

Logback 1.5.38

Fixed 1
  • In HardenedObjectInputStream, fixed a typo that prevented Throwable objects from being white-filtered
View originalRead the notes
How 1.5.38 went
1.5.37

Logback 1.5.37

Removed 1
  • Support for conditional configuration expressions evaluated with the Janino library has been removed due to numerous vulnerabilities; users should migrate to the online migration service or the <condition> element introduced in version 1.5.20
View originalRead the notes
How 1.5.37 went
1.5.36

Logback 1.5.36

Security 1
  • The 'condition' attribute in <if> elements now rejects certain references associated with ACE attacks (CVE-2026-13006); version 1.5.37 provides the full fix
View originalRead the notes
How 1.5.36 went
1.5.35

Logback 1.5.35

Added 1
  • Added ConfiguratorRank.AUTHENTICATING (rank 100), the highest configurator rank, for certified or authenticating configurators discovered via the ServiceLoader mechanism
Changed 3
  • ContextInitializer now requires that at most one AUTHENTICATING configurator exist on the classpath and aborts initialization with an error if more than one is found
  • The logback-examples module is now included in artifacts published to Maven Central
  • JoranConfigurator.makeAnotherInstance() and DefaultJoranConfigurator.performMultiStepConfigurationFileSearch() are now protected, allowing derived configurators to override them
Removed 1
  • ConsoleCharsetPropertyDefiner is no longer shipped because the Java 21 multi-release compilation of logback-core has been disabled
Security 1
  • The 'condition' attribute in <if> elements now rejects unicode escape sequences (\u and \U), closing a bypass of the prohibition on the new operator in Janino-evaluated conditions (CVE-2026-13006)
View originalRead the notes
How 1.5.35 went
1.5.34

Logback 1.5.34

Fixed 1
  • StackTraceElementProxy substitutes a dummy instance instead of throwing an IllegalArgumentException when certain StackTraceElement values returned by Throwable.getStackTrace are null
Security 1
  • HardenedObjectInputStream throws an InvalidClassException during deserialization attempts of Proxy classes, addressing a potential deserialization whitelist bypass vulnerability (CVE-2026-10532)
View originalRead the notes
How 1.5.34 went
1.5.33

Logback 1.5.33

Changed 3
  • When a conversionRule element specifies both class and converterClass attributes, the class attribute is used silently if the values match, and a warning is issued only if they differ
  • SSLSocketAppender enables hostname verification by default
  • SSLSocketAppender default SSL protocol is now TLSv1.2
Fixed 1
  • PropertiesConfiguratorModelHandler registers properties file URLs to the ConfigurationWatchList when scan is enabled, so changes are detected and reconfiguration occurs
Security 2
  • HardenedModelInputStream only deserializes a limited set of explicitly authorized classes in the java.lang and java.util packages instead of all classes in those packages
  • ViewStatusMessagesServletBase escapes special characters such as & as character entities when printing the status message field
View originalRead the notes
How 1.5.33 went
1.5.32

Logback 1.5.32

Fixed 1
  • Fixed incorrect check for dependencies contained within a parent model in DefaultProcessor, which previously scanned only the direct children
View originalRead the notes
How 1.5.32 went
1.5.31

Logback 1.5.31

Fixed 1
  • Missing META-INF/services directory in logback-classic.jar, which had rendered logback-classic 1.5.30 unusable with SLF4J
View originalRead the notes
How 1.5.31 went
1.5.30

Logback 1.5.30

Changed 1
  • Standardized code for version checking across modules
Fixed 2
  • logback-classic.jar was missing the META-INF/services directory, making it unusable with SLF4J; fixed in version 1.5.31
  • Scanning issue when an included file becomes available at a later time
View originalRead the notes
How 1.5.30 went
1.5.29

Logback 1.5.29

Fixed 1
  • Appender names and appender references are once again subject to variable substitution, reverting the change introduced in version 1.5.28
View originalRead the notes
How 1.5.29 went
1.5.28

Logback 1.5.28

Added 1
  • The <propertyConfigurator> element now admits a 'scan' attribute which can be used to override the 'scan' attribute in the <configuration> element.
Changed 1
  • Appender names or appender references are no longer subject to variable substitution.
Fixed 2
  • Fixed issue with configurations with conditionals encompassing appenders.
  • Fixed NullPointerException thrown by VersionUtil.checkForVersionEquality method occurring with GraalVM Native Images.
View originalRead the notes
How 1.5.28 went
1.5.27

Logback 1.5.27

Changed 2
  • Updated license to Eclipse Public License version 2.0 from version 1.0, retaining the GPL 2.1 dual-license
  • Refactored file scanning code for improved clarity
Fixed 2
  • Fixed missing MDC data transmitted by SocketAppender
  • In SizeAndTimeBasedRollingPolicy, modified totalSizeCap and maxFileSize comparison to take file compression into account
Removed 1
  • Removed all Receiver classes and components which were already disabled for several years
View originalRead the notes
How 1.5.27 went
1.5.26

Logback 1.5.26

Changed 1
  • Logback components now ship with properties files containing version information that survives shadow, fat, and shade jars, so logback-classic no longer warns about version mismatches in their absence
Fixed 1
  • InsertFromJNDIModelHandler no longer accesses the javax.naming package, which previously forced inclusion of the optional java.naming module
View originalRead the notes
How 1.5.26 went
1.5.25

Logback 1.5.25

Added 2
  • Added VersionUtil class to logback-core that checks for version compatibility issues and alerts the user if needed
  • Added EpochConverter to output milliseconds or seconds since epoch
Fixed 1
  • In configuration files, referencing a single undeclared appender no longer causes all referenced appenders to be skipped
Security 1
  • When processing configuration files, logback-core now only instantiates components compatible with the class expected by the encapsulating class, fixing an ACE vulnerability recorded as CVE-2026-1225
View originalRead the notes
How 1.5.25 went
1.5.24

Logback 1.5.24

Added 1
  • Added ExpressionPropertyCondition, a PropertyCondition that can evaluate boolean expressions similar to Java
View originalRead the notes
How 1.5.24 went
1.5.23

Logback 1.5.23

Fixed 2
  • File name collisions are detected at configuration time by analyzing the configuration file instead of at run time, avoiding the ConcurrentModificationException
  • ZIP and XZ compression now use a BufferedOutputStream when writing to the compressed file
View originalRead the notes
How 1.5.23 went
1.5.22

Logback 1.5.22

Changed 1
  • Internal error messages are now rate limited using a tumbling-window guard instead of a limit-counting guard
Fixed 1
  • Stack traces now take the overridden toString() method of Throwable subclasses into account when being printed
Security 1
  • Logback no longer outputs the value of a substituted variable whose name contains the case-insensitive strings "password", "secret" or "confidential", to prevent involuntary information leakage
View originalRead the notes
How 1.5.22 went
1.5.21

Logback 1.5.21

Changed 4
  • Turbo filters are now also invoked from within the Logger log(LoggingEvent) method with the contents of the LoggingEvent, typically via the fluent API, while invocations in isDebugEnabled, isInfoEnabled and similar methods remain unchanged
  • Initialization procedure simplified by removing the step that instantiates a SerializedModelConfigurator, which can still be set up as a custom configurator
  • JsonEncoder made friendlier to derivation by sub-classes
  • Superfluous buffering removed from Zip, GZ and XZ compression code
Fixed 2
  • Turbo filters are now invoked for events logged through the fluent API, addressing issue 871
  • XMLLayout thread safety issue reported in LOGBACK-427
Removed 1
  • Reentry guard removed from most subclasses of UnsynchronizedAppenderBase where it was not needed
View originalRead the notes
How 1.5.21 went
1.5.20

Logback 1.5.20

Added 1
  • The <condition> element is introduced as a recommended alternative to the deprecated 'condition' attribute, admitting custom PropertyEvaluator
Deprecated 1
  • The 'condition' attribute within the <if> element is deprecated due to potential vulnerabilities associated with dynamic Java code compilation and execution using Janino, and will be removed in 2027
View originalRead the notes
How 1.5.20 went
1.5.19

Logback 1.5.19

Changed 3
  • At initialization time, report watched configuration files more clearly
  • Soften the message regarding usage of ConsoleAppender and its potential impact on performance
  • In ViewStatusMessagesServlet, restrict processing of the "Clear" button to the POST method
Security 1
  • Disallow the "new" operator in the condition attribute of <if> elements to fix an ACE vulnerability recorded as CVE-2025-11226
View originalRead the notes
How 1.5.19 went
1.5.18

Logback 1.5.18

Added 1
  • Support for XZ compression of archived log files, using the Tukaani XZ library for Java, with GZ compression as a fallback when the XZ library is missing.
Removed 1
  • References to the deprecated java.security.AccessController class.
View originalRead the notes
How 1.5.18 went
1.5.17

Logback 1.5.17

Fixed 2
  • Jansi 2.4.0 color-coded output not working on Windows CMD.exe console when the default terminal application is set to "Windows Console Host"
  • Race condition when the MDC class is initialized while org.slf4j.LoggerFactory is initializing logback-classic's LoggerContext, causing the MDCAdapter used by MDC to not match the instance used by logback-classic
View originalRead the notes
How 1.5.17 went
1.5.16

Logback 1.5.16

Changed 1
  • logback-classic emits a warning about the removal of JaninoEventEvaluator in version 1.5.13 and suggests an online migration tool to ease migration of configuration files that depend on it
View originalRead the notes
How 1.5.16 went
View all

Discussion

If you publish Logback, you can claim this product by proving you administer its repository.