Skip to content
VulniPulse
Advisory severityMedium5.3Red Hat Linux

Medium [CVE-2026-54514] Information Disclosure via Eager DNS Resolution

This medium-severity Red Hat Linux advisory covers CVE-2026-54514 affecting Red Hat build of Quarkus 3.27.4.SP2, Red Hat build of Quarkus 3.33.2.SP2, Cryostat 4.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-54514 Source published Source updated

VulniPulse record published Record updated

CVE-2026-54514
Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open source advisory

Summary

jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.0.0 until 2.18.8, 2.21.4, and 3.1.4, JDKFromStringDeserializer constructed InetSocketAddress with new InetSocketAddress(host, port), which performs eager DNS name resolution for hostname inputs at deserialization time.

An application that binds untrusted JSON into a type containing an InetSocketAddress field issues an attacker-chosen DNS query during readValue, before any application-level validation or connect logic. The fix uses InetSocketAddress.createUnresolved(host, port), deferring DNS to an explicit connect.

This vulnerability is fixed in 2.18.8, 2.21.4, and 3.1.4. A flaw was found in jackson-databind, a library used for processing JSON data.

This vulnerability allows a remote attacker to force the application to perform an attacker-chosen DNS (Domain Name System) query. This occurs when untrusted JSON input containing specific network address information is processed, potentially leading to the disclosure of sensitive network configuration details.

Moderate: A flaw in `jackson-databind` can lead to information disclosure in Red Hat products that process untrusted JSON input. This eager DNS resolution occurs before application-level validation, potentially revealing internal network configuration details through DNS logs.

Is CVE-2026-54514 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-54514 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-54514?

Upgrade to a fixed release named by Red Hat:

  • 2.18.8
  • 2.21.4
  • 3.1.4
  • com.fasterxml.jackson.core/jackson-databind:2.21.4.redhat-00002
  • RHSA-2026:36002
  • RHSA-2026:36013

Confirm against the vendor advisory before you patch.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Fixed versions
  • 2.18.8
  • 2.21.4
  • 3.1.4
  • com.fasterxml.jackson.core/jackson-databind:2.21.4.redhat-00002
  • RHSA-2026:36002
  • RHSA-2026:36013

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Get an email when Red Hat RHEL & SELinux publishes the next one.

See Red Hat RHEL & SELinux's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat RHEL & SELinux
All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.