{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-71559 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-71559 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-71559 is a high-severity unsafe deserialization vulnerability in Apache Fory, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-71559 and fix it if it is affected.\n\nWhat it is: CVE-2026-71559 is a high-severity unsafe deserialization vulnerability in Apache Fory, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-71559 in the wild and no public exploit code.\n\nAffected product: Apache Fory. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-71559/ (Markdown: https://insights.sbomify.com/CVE-2026-71559/index.md)","id":"CVE-2026-71559","markdown":"https://insights.sbomify.com/CVE-2026-71559/index.md","name":"CVE-2026-71559","record":{"aliases":["GHSA-63m9-m4r7-4qjg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Fory Go library","requires_auth":"none","summary":"An attacker can cause a denial of service in applications using the Apache Fory Go library by sending crafted data with malformed type metadata.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"fory","vendor":"apache"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"Deserialization of Untrusted Data vulnerability in the Go implementation of Apache Fory allows an attacker to cause a denial of service by supplying crafted data containing malformed type metadata, which triggers an uncaught panic.\n\nThis issue affects Apache Fory: from 0.16.0 before 1.5.0.  Users of other language implementations are not affected.\n\nUsers are recommended to upgrade to version 1.5.0, which fixes the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Apache Fory: Uncaught panic (remote DoS) in Go meta-string decoder from untrusted metadata","id":"CVE-2026-71559","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Apache Fory: Out-of-bounds heap read in C++ struct deserializer tagged-int fast-path","id":"CVE-2026-71560"},"packages":[],"prev":{"headline":"Apache Fory: Heap type confusion in C++ polymorphic smart-pointer deserialization","id":"CVE-2026-71558"},"products":["Apache Fory"],"published":"2026-08-07","related":[{"cvss_score":9.8,"headline":"Apache Fory: Heap type confusion in C++ polymorphic smart-pointer deserialization","id":"CVE-2026-71558","kev_date_added":null,"published":"2026-08-07"},{"cvss_score":9.8,"headline":"Apache Fory, Apache Fory: Class-registration bypass through an auto-admitted SerializedLambda capturing interface","id":"CVE-2026-64606","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":9.8,"headline":"Apache Fory: Heap type confusion and out-of-bounds read/write in C++ compatible-mode field-skip paths","id":"CVE-2026-64608","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":9.8,"headline":"Apache Fory: PyFory ReduceSerializer Incomplete Policy Enforcement","id":"CVE-2026-48207","kev_date_added":null,"published":"2026-05-21"},{"cvss_score":9.8,"headline":"Apache Fory, Apache Fory: Python RCE via unguarded pickle fallback serializer in pyfory","id":"CVE-2025-61622","kev_date_added":null,"published":"2025-10-01"},{"cvss_score":9.1,"headline":"Apache Fory: Out-of-bounds heap read in C++ struct deserializer tagged-int fast-path","id":"CVE-2026-71560","kev_date_added":null,"published":"2026-08-07"},{"cvss_score":9.1,"headline":"Apache Fory, Apache Fory: Out-of-Bounds Read via sun.misc.Unsafe in zero-copy java deserialization","id":"CVE-2026-64609","kev_date_added":null,"published":"2026-07-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-07","vendors":["Apache Software Foundation"]},"summary":"An attacker can cause a denial of service in applications using the Apache Fory Go library by sending crafted data with malformed type metadata.","url":"https://insights.sbomify.com/CVE-2026-71559/"}