Skip to content
VulniPulse
Advisory severityMedium5.3Red Hat Linux

Medium [CVE-2026-54517] Information disclosure via improper JsonView filter application

This medium-severity Red Hat Linux advisory covers CVE-2026-54517 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-54517 Source published Source updated

VulniPulse record published Record updated

CVE-2026-54517
Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Summary

jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor.

From 2.21.0 until 2.21.4 and 3.1.4, in BeanDeserializer._deserializeUsingPropertyBased, the active-view (@JsonView) filter was applied only to creator properties; the regular property-buffering branch performed no prop.visibleInView(activeView) check.

A change making SetterlessProperty.isMerging() return true routed setterless Collection/Map properties through this unguarded path, so a setterless collection annotated with a restricted @JsonView is populated from attacker JSON even when the active view excludes it. This vulnerability is fixed in 2.21.4 and 3.1.4.

A remote attacker can exploit this vulnerability due to an issue in how active-view (@JsonView) filters are applied. This can lead to information disclosure, allowing an attacker to access data that should otherwise be restricted.

Moderate: A flaw in jackson-databind allows for information disclosure and an access-control bypass. This occurs because the `@JsonView` filter, intended to restrict data visibility, is not correctly applied to setterless collection and map properties during deserialization.

An attacker could exploit this to populate view-restricted properties from untrusted JSON, potentially accessing sensitive data that should be excluded by the active view.

Is CVE-2026-54517 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-54517 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-54517?

Upgrade to a fixed release named by Red Hat:

  • 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.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 publishes the next one.

See Red Hat'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
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.