CVE-2026-22018 is a difficult-to-exploit vulnerability in the Libraries component of Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition. It affects Oracle Java SE 8u481 variants, 11.0.30, 17.0.18, 21.0.10, 25.0.2, and 26; Oracle GraalVM for JDK 17.0.18 and 21.0.10; and Oracle GraalVM Enterprise Edition 21.3.17. An unauthenticated attacker with network access through multiple protocols can exploit affected library APIs, including where a web service passes attacker-supplied data to those APIs. The issue also applies to sandboxed Java Web Start applications and sandboxed Java applets that execute untrusted code while relying on the Java sandbox.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Small 4-file proof-of-concept repository illustrating CVE-2026-22018 against Jenkins Pipeline shared libraries. The core idea is not a fully automated exploit tool but a minimal demonstration of unsafe pipeline behavior: the Jenkinsfile loads an untrusted shared library using @Library('evil-library@master'), and the README explains that a malicious library can use Groovy's @Grab annotation to fetch an external Maven artifact whose static initializer executes on the Jenkins controller during compilation/loading. Repository structure: Jenkinsfile contains the vulnerable pipeline pattern; README.md provides the vulnerability description, impact, exploitation concept, and mitigation guidance; exploit_jenkins_library.py is only a placeholder/commentary file and does not implement the exploit itself; LICENSE is standard metadata. Main exploit capability is controller-side arbitrary code execution via malicious dependency resolution in a shared library, making this primarily a supply-chain/code-injection issue in Jenkins pipeline configuration. No real network callback, shell, or hardcoded C2 is implemented in code; the only fingerprintable target-like values are the shared library identifier and the example Maven coordinate shown in documentation.
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.
26 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.