CVE-2025-61879: External Control of File Name or Path
Source CVE Database V5
Not known to be exploited · CVSS 7.7 High.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Affects
- Infoblox NIOS through 9.0.7
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Feb 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
1. Restrict and monitor the creation of high-privileged accounts within Infoblox NIOS to trusted administrators only. 2. Implement strict access controls and audit logging around account management functions to detect anomalous activity. 3. Apply network segmentation to limit access to Infoblox management interfaces to authorized personnel and systems. 4. Regularly review and update user privileges to minimize the number of high-privileged users. 5. Monitor vendor advisories closely for patches or updates addressing CVE-2025-61879 and apply them promptly once available. 6. Employ file integrity monitoring on Infoblox systems to detect unauthorized file modifications. 7. Conduct regular security assessments and penetration testing focusing on account management and file write capabilities. 8. Consider deploying compensating controls such as multi-factor authentication and just-in-time access for high-privileged accounts to reduce risk.
Description
In Infoblox NIOS through 9.0.7, a High-Privileged User Can Trigger an Arbitrary File Write via the Account Creation Mechanism.