cve.bz

CVE-2026-71253 apache software foundation apache johnzon: Reflection Injection

9.8 criticalEPSS 0.4%

Critical (9.8) in apache software foundation apache johnzon. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in Apache Johnzon. ClassConverter loads & static-initializes an attacker-named class from untrusted JSON. This issue affects Apache Johnzon: from 1.0.0 before 2.2.0. Users are recommended to upgrade to version 1.3.1 (javax namespace) or 2.2.0 (jakarta specification namespace), which fixes the issue.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-10-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-470 Use of Externally-Controlled Input to Select Classes or Code (Reflection Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-71253 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-71253?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-71253?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-71253 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • apache software foundation:apache johnzon

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Johnzonfrom 2.0.0 before 2.2.0
Apache Software Foundation Apache Johnzonfrom 1.0.0 before 1.3.1

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as having an Important severity because unauthenticated remote actors can achieve arbitrary code execution when untrusted data triggers class initialization within the JVM, representing a high impact on system integrity and confidentiality. In enterprise integration environments such as Red Hat JBoss Fuse where Apache Johnzon processes external payloads, risk is constrained by whether deployed services map untrusted input into Class-typed fields. Exploitation requires both an endpoint bound to class representations and the presence of exploitable gadget classes on the application classpath.

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

ProductPackageStateAdvisory
Red Hat Fuse 7johnzon-mapperOut of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-71253.

Attack patterns (CAPEC)

  • CAPEC-138 Reflection Injection Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON