CVE-2026-71253
Description
A flaw was found in Apache Johnzon. This vulnerability allows a remote attacker to potentially execute arbitrary code by submitting a specially crafted JSON payload. Due to unsafe class loading in the ClassConverter component, the application loads and statically initializes an attacker-specified class from untrusted input.
Mitigation
--- CME Mitigation Guidance (2026-10-20) ---
The highest-value action is to restrict class loading during JSON deserialization to an explicit permit-list of safe types when deserializing into java.lang.Class fields in Johnzon Mapper: upgrade to Apache Johnzon 1.3.1 or 2.2.0 (or the fixed Johnzon Mapper builds), which restrict and guard class deserialization in ClassConverter and LazyConverterMap against loading arbitrary class names, closing crafted JSON payload containing an arbitrary class name targeting a Class-typed field. Until patched, this is a concern on applications deserializing untrusted JSON payloads into object models containing java.lang.Class typed fields, so avoid deserializing untrusted JSON into object models containing java.lang.Class fields and audit the classpath to eliminate classes with dangerous static initializers or gadget chains. As a compensating measure, enforce strict permit-list validation on incoming class name strings rather than relying on denylists to prevent arbitrary class resolution. These controls limit blast radius and contain exploitation, but they do not fix the underlying unsafe dynamic class loading defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 8.1 | N/A | 9.8 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.