0.0
NA
CVE-2026-71558
Apache Fory: Heap type confusion in C++ polymorphic smart-pointer deserialization
Description

Heap type confusion vulnerability in Apache Fory C++ deserialization. This issue affects Apache Fory C++ versions from 0.14.0 before 1.5.0. A crafted input payload can bypass type compatibility checks during polymorphic smart-pointer deserialization, causing an object of an incompatible type to be treated as the declared base type. This may result in undefined behavior and potentially lead to denial of service or arbitrary code execution. Users are recommended to upgrade to Apache Fory 1.5.0, which fixes this issue. Applications not using Apache Fory C++ polymorphic smart-pointer deserialization are not affected.

INFO

Published Date :

Aug. 7, 2026, 10:16 a.m.

Last Modified :

Aug. 7, 2026, 10:16 a.m.

Remotely Exploit :

No
Affected Products

The following products are affected by CVE-2026-71558 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Apache fory
Solution
Upgrade to Apache Fory C++ 1.5.0 to fix heap type confusion during deserialization.
  • Upgrade Apache Fory C++ to version 1.5.0.
  • Avoid polymorphic smart-pointer deserialization if upgrading is not possible.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-71558.

URL Resource
https://lists.apache.org/thread/oywndv60jwqdv6j37t7bc1qbcc4b235r
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-71558 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-71558 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-71558 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-71558 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Aug. 07, 2026

    Action Type Old Value New Value
    Added Affected [{'vendor': 'Apache Software Foundation', 'product': 'Apache Fory', 'versions': [{'status': 'affected', 'version': '0.14.0', 'lessThan': '1.5.0', 'versionType': 'semver'}], 'defaultStatus': 'unaffected'}]
    Added Description Heap type confusion vulnerability in Apache Fory C++ deserialization. This issue affects Apache Fory C++ versions from 0.14.0 before 1.5.0. A crafted input payload can bypass type compatibility checks during polymorphic smart-pointer deserialization, causing an object of an incompatible type to be treated as the declared base type. This may result in undefined behavior and potentially lead to denial of service or arbitrary code execution. Users are recommended to upgrade to Apache Fory 1.5.0, which fixes this issue. Applications not using Apache Fory C++ polymorphic smart-pointer deserialization are not affected.
    Added CWE CWE-502
    Added Reference https://lists.apache.org/thread/oywndv60jwqdv6j37t7bc1qbcc4b235r
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.