[hibernate-commits] [hibernate/hibernate-orm] 473c25: HHH-20334 Fix invalid log4j config

Branch: refs/heads/7.2 Home: https://github.com/hibernate/hibernate-orm Commit: 473c253d885e223d6983b24eafa0c6e57d2290b3 https://github.com/hibernate/hibernate-orm/commit/473c253d885e223d6983b24... Author: Yoann Rodière <yoann(a)hibernate.org&gt; Date: 2026-04-13 (Mon, 13 Apr 2026) Changed paths: M hibernate-core/src/test/resources/log4j2.properties Log Message: ----------- HHH-20334 Fix invalid log4j config Log4j 2.25 is more strict with its checks. Fix extracted from https://github.com/hibernate/hibernate-orm/commit/6c3c1684d9147cfb06c5ad9... Commit: a24f8f5ac5ab3980f260286425e9a548ca988673 https://github.com/hibernate/hibernate-orm/commit/a24f8f5ac5ab3980f260286... Author: Yoann Rodière <yoann(a)hibernate.org&gt; Date: 2026-04-13 (Mon, 13 Apr 2026) Changed paths: M settings.gradle Log Message: ----------- HHH-20334 Upgrade to Log4j 2.25.4 Technically we only: 1. Use it for testing 2. Have an API dependency in hibernate-testing, which provides some tools to work with log4j So the various CVEs are not really relevant: * https://logging.apache.org/security.html#CVE-2026-34478 * https://logging.apache.org/security.html#CVE-2026-34479 * https://logging.apache.org/security.html#CVE-2026-34481 Still, let’s avoid the noise related to automated tools reporting the problem. Compare: https://github.com/hibernate/hibernate-orm/compare/d93ed677acf5...a24f8f5... To unsubscribe from these emails, change your notification settings at https://github.com/hibernate/hibernate-orm/settings/notifications