CVE-2026-41607 is an out-of-bounds read vulnerability in the C++ JSON implementation of Apache Thrift affecting versions before 0.23.0. The flaw can cause reads outside valid memory boundaries, potentially exposing memory contents or causing application instability. The specific vulnerable function and triggering input are not identified. Apache Thrift 0.23.0 fixes the issue.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An out-of-bounds read vulnerability affecting Apache Thrift versions before 0.23.0. The listed CVSS v3 score is 9.1, indicating network-based exploitation without authentication or user interaction, with high confidentiality and availability impacts. The advisory recommends Apache Thrift 0.23.0; the Echo package remediation is thrift 0.19.0-4+e1 or later. The plugin states that no known exploits are available.
No vulnerability details are provided beyond a reference to a SUSE advisory.
A vulnerability referenced by the SUSE-SU-2026:3714-1 advisory; no technical details are provided in the content.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.