# CVE-2025-68462: Information disclosure in FreedomBox

> An attacker can read database dump files due to improper permissions on the backups-data directory in FreedomBox.

- **Severity:** Low 3.2 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Dec 2025
- **Updated:** 18 Dec 2025
- **Also known as:** DEBIAN-CVE-2025-68462, GHSA-gjwv-45pm-f62j, UBUNTU-CVE-2025-68462

## What is CVE-2025-68462?

CVE-2025-68462 is a low-severity vulnerability in Debian FreedomBox, published on 18 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Freedombox before 25.17.1 does not set proper permissions for the backups-data directory, allowing the reading of dump files of databases.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2025-68462?


## How do I fix CVE-2025-68462?

Upgrade to a fixed version.

## Is CVE-2025-68462 being exploited?

There is no known exploitation of CVE-2025-68462 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68462 and fix it if it is affected.

What it is: CVE-2025-68462 is a low-severity vulnerability in Debian FreedomBox, published on 18 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68462 in the wild and no public exploit code.

Affected product: Debian FreedomBox. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68462/ (Markdown: https://insights.sbomify.com/CVE-2025-68462/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68462
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68462
- OSV: https://osv.dev/vulnerability/CVE-2025-68462

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68462/
Summaries are generated and may contain mistakes; the official description above is the record.