Skip to main content
Mallory
UnratedPublic exploitVulnerability

CVE-2026-39949

Updated 5 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
IdentifiersCVE-2026-39949
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2026-39949This repository is a small standalone Python proof-of-concept exploit for authenticated remote code execution in Cacti via host variable injection, identified as CVE-2026-39949. The repo contains only two files: a README describing the vulnerability and usage, and a single executable script, cacti_rce_poc.py, which is the main entry point. The exploit automates the full attack chain against a Cacti web application. It authenticates to the target using supplied credentials, retrieves CSRF tokens from Cacti forms, creates a new device/host with a malicious payload embedded in the notes field, creates a graph template whose right_axis_label references the |host_notes| variable, creates a graph using that template, and finally requests /graph_image.php to force graph rendering. The vulnerability is exploited because the host notes value is substituted into RRDtool command-line arguments without sanitization, allowing shell metacharacter injection. Capabilities include arbitrary command execution in direct mode and out-of-band verification/exfiltration in OOB mode. In direct mode, the script injects the operator-provided command, defaulting to `id`. In OOB mode, it builds a curl command that sends base64-encoded command output to an attacker-controlled HTTP endpoint. The payload is hardcoded shell command injection rather than a reusable framework payload, so the exploit is best classified as OPERATIONAL rather than weaponized. The code uses Python standard library modules only: argparse, urllib.request, urllib.parse, http.cookiejar, re, sys, and time. There is no external framework dependency. The main network interaction is with the target Cacti instance over HTTP(S), specifically the endpoints /index.php, /host.php, /graph_templates.php, /graphs_new.php, and /graph_image.php. The script also optionally causes the target to contact an attacker-controlled OOB domain over HTTP. Notable implementation details: session handling is done with a cookie jar; successful login is inferred by the presence of a cookie containing 'cacti'; CSRF tokens are extracted from HTML using a regex for __csrf_magic; created object IDs are parsed from redirect URLs or returned HTML. The exploit is clearly intended for real exploitation, not just detection, and there are no obvious signs of it being fake or destructive beyond the intended command execution behavior.lukehebe · Disclosed Jun 16, 2026 · python · markdown · web · networkOperational
FAQ

Frequently asked questions

Is CVE-2026-39949 exploited in the wild?
Yes. As of Jun 17, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-39949?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-39949, the earliest disclosed Jun 16, 2026.
Activity feed

Recent activity

2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.