CVE-2025-68462: Debian FreedomBox · Incorrect Permissions
Affects Debian FreedomBoxSource CVE Database V5
Not known to be exploited · CVSS 3.2 Low : upgrade to 25.17.1 when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 25.17.1
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Dec 2025
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 2026-10-26.
What to do
Upgrade debian/freedombox to 25.17.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Debiandebian/freedomboxpkg:deb/debian/freedomboxOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Upgrade FreedomBox installations to version 25.17.1 or later as soon as the patch is available to ensure correct permission settings on the backups-data directory. 2. Conduct an immediate audit of file system permissions on backup directories to verify that only authorized users have read access. 3. Restrict local user accounts and enforce the principle of least privilege to minimize the risk of unauthorized local access. 4. Implement monitoring and alerting for unusual local access to backup directories or database dump files. 5. Consider encrypting backup files at rest to add an additional layer of protection in case of unauthorized access. 6. Review and harden FreedomBox configurations related to user access and backup management. 7. Educate users and administrators about the risks of local access vulnerabilities and the importance of timely patching. 8. If FreedomBox is deployed in multi-user or shared environments, isolate backup storage using access control mechanisms or containerization to reduce exposure.
Description
Freedombox before 25.17.1 does not set proper permissions for the backups-data directory, allowing the reading of dump files of databases.