[hibernate-commits] [hibernate/hibernate-orm] 379c8b: HHH-20334 Fix invalid log4j config

Branch: refs/heads/7.1 Home: https://github.com/hibernate/hibernate-orm Commit: 379c8b454f25f60cf822f68de52fd1b431e29215 https://github.com/hibernate/hibernate-orm/commit/379c8b454f25f60cf822f68... 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: 7b10d2c8fe07480a6f98fa13821b0ee5c3506e4f https://github.com/hibernate/hibernate-orm/commit/7b10d2c8fe07480a6f98fa1... 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/61690a57b2cd...7b10d2c... To unsubscribe from these emails, change your notification settings at https://github.com/hibernate/hibernate-orm/settings/notifications