Skip to main content

Apache Fory CVE-2026-71558

| EUVDEUVD-2026-54422 CRITICAL
Deserialization of Untrusted Data (CWE-502)
2026-08-07 apache GHSA-rwv5-p9fv-c8fp
9.8
CVSS 3.1 · Vendor: apache
Share

Severity by source

Vendor (apache) PRIMARY
9.8 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
8.1 HIGH

Network-reachable and unauthenticated once the polymorphic path is exposed (AV:N/PR:N), but reliable exploitation of heap type confusion into code execution is build-dependent and feature-gated, so AC:H; full C/I/A impact on the process.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (apache).

CVSS VectorVendor: apache

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

6
Analysis Updated
Aug 07, 2026 - 18:28 vuln.today
v2 (cvss_changed)
Re-analysis Queued
Aug 07, 2026 - 18:22 vuln.today
cvss_changed
CVSS changed
Aug 07, 2026 - 18:22 NVD
9.8 (CRITICAL)
Patch available
Aug 07, 2026 - 10:16 EUVD
Analysis Generated
Aug 07, 2026 - 09:46 vuln.today
CVE Published
Aug 07, 2026 - 08:54 cve.org
HIGH

DescriptionCVE.org

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.

AnalysisAI

Heap type confusion in the Apache Fory C++ deserialization engine (versions 0.14.0 up to but not including 1.5.0) lets a crafted payload bypass type-compatibility checks during polymorphic smart-pointer deserialization, so an object of an incompatible type is handled as its declared base type. Because CWE-502 untrusted-data handling here corrupts memory rather than merely mis-parsing values, an attacker who controls serialized input can trigger undefined behavior ranging from denial of service to arbitrary code execution. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Reach Fory C++ deserialization endpoint
Delivery
Deliver crafted polymorphic smart-pointer payload
Exploit
Bypass type-compatibility check
Execution
Trigger heap type confusion
Persist
Corrupt object layout / vtable dispatch
Impact
Crash service or execute arbitrary code

Vulnerability AssessmentAI

Exploitation The application must actively use Apache Fory C++ polymorphic smart-pointer deserialization (deserializing base-class smart pointers such as shared_ptr/unique_ptr where the concrete type is chosen from the payload) on input an attacker can control - the vendor explicitly states applications not using this feature are not affected. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The signals are mixed. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An attacker sends a service a Fory-serialized payload that declares a polymorphic smart pointer to some base class but embeds a type descriptor for an incompatible concrete type, slipping past the compatibility check. On deserialization the C++ runtime constructs and dispatches through the wrong object layout, corrupting the heap; in the simplest case this crashes the service (DoS), and with a carefully engineered payload the type confusion could be steered toward arbitrary code execution. …
Remediation Vendor-released patch: upgrade Apache Fory to 1.5.0, which contains the fix, per the Apache advisory (https://lists.apache.org/thread/oywndv60jwqdv6j37t7bc1qbcc4b235r) and the oss-security announcement (http://www.openwall.com/lists/oss-security/2026/08/07/3). … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours, inventory all systems using Apache Fory versions 0.14.0 through 1.4.x and identify which ones process untrusted serialized input. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-71558 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy