Loading vulnerability…
CVE-2026-48017 is a remote code execution vulnerability in DbGate affecting versions 7.1.8 and earlier. The flaw is in the POST /runners/load-reader endpoint, which accepts a functionName parameter and directly interpolates it into a JavaScript code template without sanitization or validation. Because the attacker-controlled value is used to generate executable JavaScript, an authenticated user with only basic access can inject arbitrary JavaScript that runs on the server with the full privileges of the DbGate Node.js process. The issue also bypasses the intended require=null sandbox restriction, making the code-generation path effectively unsafe for unprivileged authenticated users.
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 PoC repository with 2 files: a README documenting CVE-2026-48017 in DbGate and a single Python exploit script at poc/rce_loadreader_functionname_injection.py. The exploit is a standalone Python requests-based authenticated RCE PoC, not tied to a larger exploitation framework. It targets DbGate's POST /runners/load-reader endpoint, where attacker-controlled functionName is interpolated into a JavaScript template executed in a forked runner process. The script optionally authenticates via POST /auth/login to obtain a JWT, then sends JSON containing a malicious functionName and empty props object. The injected JavaScript uses process.binding("spawn_sync") to bypass the intended require=null sandbox and launch /bin/sh -c <command>, enabling arbitrary command execution on the server. Repository purpose is clearly offensive validation / defender reproduction of the vulnerability rather than detection only. The code is operational because it accepts a user-supplied command and can either use an existing JWT or log in first, but it is still a simple PoC rather than a weaponized framework module.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.