Loading vulnerability…
CVE-2026-33331 is a stored cross-site scripting vulnerability in oRPC's OpenAPI documentation generation affecting versions prior to 1.13.9. If an attacker can control a field in the OpenAPI specification, such as info.description, they can inject content that breaks out of the JSON context used by the generated API documentation and causes arbitrary JavaScript to execute in the browser when the documentation is viewed. The flaw is persistent because the malicious payload is stored in the generated specification or documentation content and is triggered whenever a user opens the affected API documentation.
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 Node.js proof-of-concept lab for CVE-2026-33331, a stored XSS issue in middleapi/oRPC OpenAPI Reference generation prior to v1.13.9. The core issue is unsafe embedding of an OpenAPI spec into an HTML <script type="application/json"> element using raw JSON.stringify() without escaping HTML-sensitive characters such as <, >, /, &, and '. An attacker-controlled field like info.description can inject </script><script>...</script>, terminate the JSON script block early, and execute arbitrary JavaScript in the browser when a victim views the generated docs. Repository structure: README.md explains the vulnerability, impact, setup, and patch. app/server.js is the main lab application using Express; it exposes /docs (vulnerable), /docs/safe (patched), /spec.json (raw spec), and / (redirect). The vulnerable renderer intentionally embeds JSON.stringify(spec) directly into a script tag and includes a malicious description payload that triggers alert(). The patched renderer demonstrates the fix by Unicode-escaping dangerous characters before embedding JSON and parsing it safely. app/package.json defines a minimal Express dependency set. app/Dockerfile and docker-compose.yml provide a containerized lab that publishes port 3000 and health-checks /docs. poc/exploit.js is a standalone minimal HTTP server that reproduces the same bug without Express or the full lab context. Exploit capability: this is a browser/web exploit demonstration, not a remote shell or post-exploitation tool. Its purpose is to prove stored XSS in generated API docs. The included payload is basic but functional: it executes alert() in the victim browser. The README also notes realistic impact such as session theft, arbitrary API actions in the victim context, and phishing overlays, though those are not implemented in code. Overall, this is a legitimate educational exploit repository with runnable code that reproduces the vulnerability locally and contrasts vulnerable versus patched behavior.
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.