CVE-2026-34477

medium

Published 2026-04-10 · Modified 2026-04-17

💬 Discuss on Community ✚ Propose mitigation

CVSS v3

5.9

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

CVSS v4 NEW

6.3

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

VIR risk

5.9

Description

Apache Log4j Core: `verifyHostName` attribute silently ignored in TLS configuration

Predictions

Exploit likelihood

69%

Patch ETA

—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

SUSE Affected 1 release

Version	Status	Fixed in
—	Affected	—

Debian Fixed 5 releases

Version	Status	Fixed in
trixie	Fixed	`0`
sid	Fixed	`0`
forky	Fixed	`0`
bullseye	Fixed	`0`
bookworm	Fixed	`0`

Package impact

Ecosystem	Package	Vulnerable	Fixed
Maven	org.apache.logging.log4j:log4j-core	`>=2.12.0,<2.25.4`	`2.25.4`
Maven	org.apache.logging.log4j:log4j-core	`>=3.0.0-alpha1,<=3.0.0-beta3`

Application impact

Vendor	Product	Versions	Fixed
apache	log4j	`{"startIncluding":"2.12.0","endExcluding":"2.25.4"}`	`2.25.4`
apache	log4j	`3.0.0`

References

CWEs

CWE-297 CWE-295

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.