# CVE-2026-97025: Flatpak: flatpak: world-readable oci authentication token in system-helper cache path

> Local attackers can read world-readable OCI authentication tokens from the Flatpak system-helper cache to impersonate users against OCI repositories.

- **Severity:** Low 3.2 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 28 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-97025, UBUNTU-CVE-2026-97025

## What is CVE-2026-97025?

CVE-2026-97025 is a low-severity vulnerability in Red Hat Enterprise Linux 10, published on 28 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Flatpak writes the OCI repository authentication token with world-readable permissions (0644) in the system-helper's cache directory, allowing other local users on a multi-user system to read the token and impersonate the authenticated user against the OCI repository. Only OCI-based sources (e.g. as used by Fedora) are affected; libostree-based sources such as Flathub are not.

Weakness: CWE-378 (Creation of Temporary File With Insecure Permissions)

## Which versions are affected by CVE-2026-97025?


## How do I fix CVE-2026-97025?

Apply the vendor's patch.

## Is CVE-2026-97025 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97025 and fix it if it is affected.

What it is: CVE-2026-97025 is a low-severity vulnerability in Red Hat Enterprise Linux 10, published on 28 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-97025 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. 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-2026-97025/ (Markdown: https://insights.sbomify.com/CVE-2026-97025/index.md)
```

## Sources

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

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