Skip to content
VulniPulse
Advisory severityMedium5.3Red Hat Linux

Medium [CVE-2026-54515] Ignored properties can be unexpectedly modified

This medium-severity Red Hat Linux advisory covers CVE-2026-54515 affecting Red Hat build of Quarkus 3.27.4.SP2, Red Hat build of Quarkus 3.33.2.SP2, Red Hat JBoss Enterprise Application Platform 7.4.25.

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

CVE-2026-54515 Source published Source updated

VulniPulse record published Record updated

CVE-2026-54515
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.8.0 until 2.18.9, 2.21.5, and 3.1.4, in BeanDeserializerBase.createContextual(), per-property @JsonIgnoreProperties exclusions are applied by _handleByNameInclusion(), producing a contextual deserializer whose BeanPropertyMap has the ignored properties removed.

The subsequent per-property case-insensitivity block (triggered by @JsonFormat(ACCEPT_CASE_INSENSITIVE_PROPERTIES)) rebuilds from this._beanProperties (the original, unfiltered map) instead of contextual._beanProperties, then overwrites the filtered map — restoring every property _handleByNameInclusion had just removed.

This vulnerability is fixed in 2.18.9, 2.21.5, and 3.1.4. This vulnerability occurs in the data-binding functionality where properties intended to be ignored are incorrectly restored and become writable again.

An attacker could potentially exploit this by providing input that modifies data through these supposedly ignored properties. This could lead to unintended changes in application data, impacting data integrity.

This is a Moderate impact flaw in jackson-databind where applications enabling case-insensitive property matching alongside per-property @JsonIgnoreProperties may inadvertently expose fields to unauthorized modification.

Is CVE-2026-54515 exploited?

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

Upgrade to a fixed release named by Red Hat:

  • 2.18.9
  • 2.21.5
  • 3.1.4
  • com.fasterxml.jackson.core/jackson-databind:2.21.4.redhat-00002
  • com.fasterxml.jackson.core/jackson-databind:2.18.8.redhat-00003
  • eap7-activemq-artemis-0:2.16.0-23.redhat_00058.1.el7eap
  • eap7-jackson-annotations-0:2.18.9-1.redhat_00003.1.el7eap
  • eap7-jackson-core-0:2.18.9-1.redhat_00003.1.el7eap
  • eap7-jackson-databind-0:2.18.9-1.redhat_00003.1.el7eap
  • eap7-jackson-jaxrs-providers-0:2.18.9-1.redhat_00003.1.el7eap
  • eap7-jackson-modules-base-0:2.18.9-1.redhat_00003.1.el7eap
  • eap7-jackson-modules-java8-0:2.18.9-1.redhat_00003.1.el7eap

38 more fixed releases are listed below.

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.9
  • 2.21.5
  • 3.1.4
  • com.fasterxml.jackson.core/jackson-databind:2.21.4.redhat-00002
  • com.fasterxml.jackson.core/jackson-databind:2.18.8.redhat-00003
  • eap7-activemq-artemis-0:2.16.0-23.redhat_00058.1.el7eap
  • eap7-jackson-annotations-0:2.18.9-1.redhat_00003.1.el7eap
  • eap7-jackson-core-0:2.18.9-1.redhat_00003.1.el7eap
  • eap7-jackson-databind-0:2.18.9-1.redhat_00003.1.el7eap
  • eap7-jackson-jaxrs-providers-0:2.18.9-1.redhat_00003.1.el7eap
  • eap7-jackson-modules-base-0:2.18.9-1.redhat_00003.1.el7eap
  • eap7-jackson-modules-java8-0:2.18.9-1.redhat_00003.1.el7eap
  • eap7-wildfly-0:7.4.25-6.GA_redhat_00005.1.el7eap
  • eap7-activemq-artemis-0:2.16.0-23.redhat_00058.1.el8eap
  • eap7-jackson-annotations-0:2.18.9-1.redhat_00003.1.el8eap
  • eap7-jackson-core-0:2.18.9-1.redhat_00003.1.el8eap
  • eap7-jackson-databind-0:2.18.9-1.redhat_00003.1.el8eap
  • eap7-jackson-jaxrs-providers-0:2.18.9-1.redhat_00003.1.el8eap
  • eap7-jackson-modules-base-0:2.18.9-1.redhat_00003.1.el8eap
  • eap7-jackson-modules-java8-0:2.18.9-1.redhat_00003.1.el8eap
  • eap7-wildfly-0:7.4.25-6.GA_redhat_00005.1.el8eap
  • eap7-activemq-artemis-0:2.16.0-23.redhat_00058.1.el9eap
  • eap7-jackson-annotations-0:2.18.9-1.redhat_00003.1.el9eap
  • eap7-jackson-core-0:2.18.9-1.redhat_00003.1.el9eap
  • eap7-jackson-databind-0:2.18.9-1.redhat_00003.1.el9eap
  • eap7-jackson-jaxrs-providers-0:2.18.9-1.redhat_00003.1.el9eap
  • eap7-jackson-modules-base-0:2.18.9-1.redhat_00003.1.el9eap
  • eap7-jackson-modules-java8-0:2.18.9-1.redhat_00003.1.el9eap
  • eap7-wildfly-0:7.4.25-6.GA_redhat_00005.1.el9eap
  • com.fasterxml.jackson.core/jackson-databind:2.18.9.redhat-00003
  • eap8-activemq-artemis-0:2.40.0-8.redhat_00024.1.el10eap
  • eap8-apache-cxf-0:4.1.7-1.SP1_redhat_00001.1.el10eap
  • eap8-artemis-wildfly-integration-0:2.0.5-1.Final_redhat_00001.1.el10eap
  • eap8-bouncycastle-0:1.85.0-1.redhat_00001.1.el10eap
  • eap8-cryptacular-0:1.2.7-1.redhat_00002.1.el10eap
  • eap8-eap-product-conf-parent-0:801.8.0-1.GA_redhat_00001.1.el10eap
  • eap8-hibernate-0:6.6.54-1.Final_redhat_00001.1.el10eap
  • eap8-httpcomponents-asyncclient-0:4.1.5-5.redhat_00008.1.el10eap
  • eap8-ironjacamar-0:3.0.22-1.Final_redhat_00001.1.el10eap
  • eap8-jackson-annotations-0:2.18.9-1.redhat_00003.1.el10eap
  • eap8-jackson-core-0:2.18.9-1.redhat_00003.1.el10eap
  • eap8-jackson-databind-0:2.18.9-1.redhat_00003.1.el10eap
  • eap8-jackson-dataformats-text-0:2.18.9-1.redhat_00003.1.el10eap
  • RHSA-2026:36002
  • RHSA-2026:36013
  • RHSA-2026:67603
  • RHSA-2026:67604
  • RHSA-2026:70277
  • RHSA-2026:70230
  • RHSA-2026:70228

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.