Loading vulnerability…
CVE-2026-63039 is an SQL injection vulnerability in Apache InLong affecting versions 2.0.0 through before 2.4.0. The flaw is caused by improper neutralization of special elements used in SQL commands and is associated with unvalidated MyBatis dollar-sign interpolation in the AuditAlertRuleService component. By supplying crafted string input that is incorporated directly into an SQL statement, an attacker can alter the intended query structure and trigger SQL injection against the backend database.
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 runnable Java/MyBatis proof-of-concept reproducer for CVE-2026-63039, an ORDER BY SQL injection in Apache InLong manager's AuditAlertRule query path. It is not part of a larger exploit framework. The core issue is faithfully reproduced in `src/main/resources/mappers/AuditAlertRuleEntityMapper.xml`, where safe `#{}` bindings are used for filters but attacker-controlled `request.orderField` and `request.orderType` are inserted directly with MyBatis `${}` in `order by ${request.orderField} ${request.orderType}`. Repository structure: `ExploitMain.java` is the main entry point and drives the demonstration; `AuditAlertRulePageRequest.java`, `AuditAlertRuleEntity.java`, and `AuditAlertRuleEntityMapper.java` are minimal stand-ins for the corresponding InLong classes; `AuditAlertRuleEntityMapper.xml` contains the vulnerable SQL sink; `mybatis-config.xml` defines the JDBC/MyBatis configuration; `init.sql` seeds a demo MySQL schema with `audit_alert_rule` and a separate `manager_secrets` table; `docker-compose.yml` launches MySQL and the reproducer; `Dockerfile` packages the one-shot Java app; `README.md` explains the vulnerability and expected output. Exploit capability: the PoC first performs a benign query, then sends a malicious `orderField` containing the hardcoded SQL payload `extractvalue(1,concat(0x7e,(select secret_value from manager_secrets limit 1)))`. When the vulnerable mapper executes the ORDER BY clause, MySQL evaluates the expression and raises an XPATH error embedding the selected secret. `ExploitMain.extractSecretFromXpathError()` parses the exception message and prints the leaked value, demonstrating arbitrary SQL expression execution and cross-table data disclosure. The exploit is operational but narrowly scoped: it uses a fixed payload and local Dockerized MySQL environment rather than a generalized remote delivery mechanism. Primary target conditions: Apache InLong manager versions before 2.4.0, specifically the AuditAlertRule query path where user input can reach `orderField`/`orderType` without allowlist validation, backed by MySQL. The included demo uses MySQL 8.0 with root/inlong credentials and database `apache_inlong_manager`.
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.
1 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.