Loading vulnerability…
CVE-2026-0303 is an arbitrary code-execution vulnerability in Palo Alto Networks Checkov by Prisma Cloud. When scanning a directory, Checkov can automatically load a configuration file from that directory. An attacker-controlled configuration file can cause arbitrary code to execute in the security context of the user or automation process running Checkov.
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 seven-file Python/Docker proof of concept demonstrates CVE-2026-0303, an arbitrary-code-execution issue in vulnerable Checkov releases. The exploit directory contains an auto-discovered .checkov.yml that sets external-checks-dir to /workspace/external-checks. During a Terraform scan, Checkov imports poc_check.py as an external check; its top-level exploit() invocation runs immediately, before the nominal ProofOfImportCheck policy object is used. The payload connects to host.docker.internal on TCP port 4545, duplicates the socket onto file descriptors 0, 1, and 2, and invokes /bin/sh -i, producing a reverse shell. The included main.tf is benign Terraform content that provides an aws_s3_bucket resource for scanning. Dockerfile and compose.yaml build a Checkov 3.2.531 lab container, mount exploit/ read-only at /workspace, and retain a writable /tmp tmpfs. This is an operational PoC with a basic hard-coded listener endpoint, rather than a detection-only script.
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.