CVE-2025-46068: Unrestricted File Upload
Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2025-46068, organizations should immediately restrict network access to the Automai Director update mechanism, ideally isolating it from untrusted networks. Implement network segmentation and firewall rules to limit inbound and outbound connections related to the update process. Monitor network traffic for unusual or unauthorized update requests. Until a vendor patch is released, consider disabling automatic updates or manually verifying update sources if feasible. Employ application whitelisting and endpoint detection and response (EDR) solutions to detect and block suspicious code execution. Maintain up-to-date backups and ensure incident response plans are prepared for potential exploitation scenarios. Engage with the vendor to obtain patches or official guidance as soon as they become available. Conduct thorough audits of systems running Automai Director to identify and remediate any signs of compromise.
Description
An issue in Automai Director v.25.2.0 allows a remote attacker to execute arbitrary code via the update mechanism