CVE-2026-68496

Description

A flaw was found in the Smile parser of jackson-dataformats-binary. The parser fails to enforce configured property name length limits when decoding object property names. A remote attacker can exploit this vulnerability by submitting a specially crafted Smile document containing an excessively long property name. This triggers unbounded memory allocation, leading to memory exhaustion and a Denial of Service (DoS).

Statement

Red Hat rates this flaw as Important because an unauthenticated remote attacker can exhaust system heap memory and cause an application-wide denial of service by submitting a single payload. Exploitation requires that an application endpoint is configured to consume binary Smile-encoded input, which is not the standard data format for most default REST services. While standard JSON parsers enforce property size limits, deployments running services or integration routes that explicitly process Smile documents remain exposed to memory exhaustion under default configurations.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.5N/A7.5
Attack VectorNetworkN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactNoneN/ANone
Availability ImpactHighN/AHigh

Vector

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

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)

When allocating resources without limits, an attacker could prevent other systems, applications, or processes from accessing the same type of resource. It can be easy for an attacker to consume many resources by rapidly making many requests or causing larger resources to be used than is needed.

Frequently Asked Questions

Want to get errata notifications? Sign up here.