Loading vulnerability…
CVE-2026-22011 is a vulnerability in Oracle Applications DBA, specifically the ADPatch component of Oracle E-Business Suite. Affected versions are 12.2.3 through 12.2.15. The issue is described as difficult to exploit and is reachable over the network via HTTP by an attacker who already has high privileges. Exploitation also requires human interaction by a user other than the attacker. Successful exploitation can compromise Oracle Applications DBA and, because the vulnerability has scope change, the impact may extend beyond the vulnerable component to additional products or environments connected to it.
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.
This repository is a small proof-of-concept/operational exploit demonstrating insecure iOS MDM profile delivery over HTTP, labeled as CVE-2026-22011. The structure is minimal: a Python Flask server (mdm_server.py), a malicious configuration profile (profile.mobileconfig), a README describing the attack, and a license file. The main exploit logic is in mdm_server.py, which starts a Flask app bound to 0.0.0.0 on port 80 and exposes the /enroll.mobileconfig route. When accessed, that route serves profile.mobileconfig with the Apple configuration profile MIME type application/x-apple-aspen-config. The profile itself contains an attacker-controlled MDM URL, http://attacker.com/mdm, indicating the intended next-stage enrollment target. The exploit capability is straightforward: it hosts a malicious MDM enrollment profile over plain HTTP so a victim device can be tricked into downloading it, or so an on-path attacker can replace a legitimate profile with this malicious one. If the victim installs the profile, the attacker may gain device management privileges through rogue MDM enrollment. This is not a scanner or detector; it is a delivery mechanism for a malicious configuration payload. There is no advanced automation, evasion, or post-exploitation logic in the repository, but it does provide a working payload and hosting component, making it more than a pure PoC. The attack vectors are web/network-based, relying on insecure transport, social engineering, or man-in-the-middle conditions rather than memory corruption or local code execution.
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.