Loading vulnerability…
CVE-2026-63317 is an arbitrary class instantiation vulnerability in Apache OpenNLP caused by multiple code paths that accept a fully qualified class name from attacker-influenced input, call Class.forName(), and invoke a no-argument constructor without validating the class name or enforcing an expected safe type boundary before loading. The affected paths include GeneratorFactory processing of XML feature generator descriptors embedded in model archives, StreamFactoryRegistry.getFactory(Class, String) fallback handling of unregistered format names as ObjectStreamFactory class names, and StringInterners loading of an interner implementation from a system property. The most practically exposed paths are model loading from crafted archives and applications that pass untrusted format names into OpenNLP tooling or APIs. Successful exploitation depends on the presence on the application classpath of a class whose static initializer or no-argument constructor performs attacker-useful side effects such as JNDI activity, outbound network access, or filesystem interaction. The issue therefore enables unsafe class loading and initialization rather than guaranteed standalone remote code execution.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.