Loading vulnerability…
CVE-2024-38526 affects pdoc, an API documentation generator for Python projects. When documentation was generated with the --math option, the output included references to JavaScript hosted on the polyfill.io CDN. After control of polyfill.io changed, the service began serving malicious code, causing generated documentation to load untrusted third-party JavaScript. The vulnerability is therefore a supply-chain style issue in which pdoc-generated documentation could embed and execute attacker-controlled script in users' browsers when the affected documentation is viewed. The issue was fixed in pdoc 14.5.1.
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.
--math option from affected pdoc versions, or remove the external polyfill.io script reference from generated output before publication. Restricting or sanitizing third-party script inclusion through Content Security Policy may reduce exposure, but the primary mitigation is to eliminate the dependency on the compromised external script and upgrade to the fixed release.Patch, then assume compromise.
--math option so that stale vulnerable output no longer references the malicious third-party resource.No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
3 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.