# CVE-2025-9615: Networkmanager: networkmanager file access > NetworkManager allows non-root users to access files owned by other users due to improper privilege handling, potentially leading to data exposure or privilege escalation. - **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/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:** Not needed - **Fix available:** Yes - **Published:** 26 Jan 2026 - **Updated:** 30 Jun 2026 - **Also known as:** ALSA-2026:18142, ALSA-2026:18597, DEBIAN-CVE-2025-9615, GHSA-w24g-6mf8-65cj, OESA-2026-1571, RHSA-2026:18142, RHSA-2026:18597, RLSA-2026:18142, RLSA-2026:18597, SUSE-SU-2026:1419-1, SUSE-SU-2026:1420-1, SUSE-SU-2026:1427-1, SUSE-SU-2026:1443-1, SUSE-SU-2026:21113-1, SUSE-SU-2026:21121-1, SUSE-SU-2026:22047-1, SUSE-SU-2026:22086-1, UBUNTU-CVE-2025-9615, openSUSE-SU-2025:15822-1, openSUSE-SU-2026:10051-1, openSUSE-SU-2026:10295-1, openSUSE-SU-2026:11104-1, openSUSE-SU-2026:20911-1 ## What is CVE-2025-9615? CVE-2025-9615 is a low-severity missing authorization vulnerability in Red Hat Enterprise Linux 10, published on 26 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description A flaw was found in NetworkManager. The NetworkManager package allows access to files that may belong to other users. NetworkManager allows non-root users to configure the system's network. The daemon runs with root privileges and can access files owned by users different from the one who added the connection. Weakness: CWE-281 (Improper Preservation of Permissions) ## Which versions are affected by CVE-2025-9615? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `NetworkManager` | AlmaLinux:10 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-adsl` | AlmaLinux:10 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-bluetooth` | AlmaLinux:10 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-cloud-setup` | AlmaLinux:10 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-config-connectivity-redhat` | AlmaLinux:10 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-config-server` | AlmaLinux:10 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-libnm` | AlmaLinux:10 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-libnm-devel` | AlmaLinux:10 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-ovs` | AlmaLinux:10 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-ppp` | AlmaLinux:10 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-tui` | AlmaLinux:10 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-wifi` | AlmaLinux:10 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-wwan` | AlmaLinux:10 | All versions | 1:1.56.0-1.el10 | | `NetworkManager` | AlmaLinux:9 | All versions | 1:1.54.3-2.el9 | | `NetworkManager-adsl` | AlmaLinux:9 | All versions | 1:1.54.3-2.el9 | | `NetworkManager-bluetooth` | AlmaLinux:9 | All versions | 1:1.54.3-2.el9 | | `NetworkManager-cloud-setup` | AlmaLinux:9 | All versions | 1:1.54.3-2.el9 | | `NetworkManager-config-connectivity-redhat` | AlmaLinux:9 | All versions | 1:1.54.3-2.el9 | | `NetworkManager-config-server` | AlmaLinux:9 | All versions | 1:1.54.3-2.el9 | | `NetworkManager-dispatcher-routing-rules` | AlmaLinux:9 | All versions | 1:1.54.3-2.el9 | | `NetworkManager-initscripts-updown` | AlmaLinux:9 | All versions | 1:1.54.3-2.el9 | | `NetworkManager-libnm` | AlmaLinux:9 | All versions | 1:1.54.3-2.el9 | | `NetworkManager-libnm-devel` | AlmaLinux:9 | All versions | 1:1.54.3-2.el9 | | `NetworkManager-ovs` | AlmaLinux:9 | All versions | 1:1.54.3-2.el9 | | `NetworkManager-ppp` | AlmaLinux:9 | All versions | 1:1.54.3-2.el9 | | `NetworkManager-team` | AlmaLinux:9 | All versions | 1:1.54.3-2.el9 | | `NetworkManager-tui` | AlmaLinux:9 | All versions | 1:1.54.3-2.el9 | | `NetworkManager-wifi` | AlmaLinux:9 | All versions | 1:1.54.3-2.el9 | | `NetworkManager-wwan` | AlmaLinux:9 | All versions | 1:1.54.3-2.el9 | | `NetworkManager` | Red Hat:enterprise_linux:10.2 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-adsl` | Red Hat:enterprise_linux:10.2 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-adsl-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-bluetooth` | Red Hat:enterprise_linux:10.2 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-bluetooth-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-cloud-setup` | Red Hat:enterprise_linux:10.2 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-cloud-setup-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-config-connectivity-redhat` | Red Hat:enterprise_linux:10.2 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-config-server` | Red Hat:enterprise_linux:10.2 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 1:1.56.0-1.el10 | | `NetworkManager-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 1:1.56.0-1.el10 | ## How do I fix CVE-2025-9615? Apply the vendor's patch. ## Is CVE-2025-9615 being exploited? There is no known exploitation of CVE-2025-9615 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-9615 and fix it if it is affected. What it is: CVE-2025-9615 is a low-severity missing authorization vulnerability in Red Hat Enterprise Linux 10, published on 26 Jan 2026. 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-9615 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-2025-9615/ (Markdown: https://insights.sbomify.com/CVE-2025-9615/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-9615 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-9615 - OSV: https://osv.dev/vulnerability/CVE-2025-9615 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-9615/ Summaries are generated and may contain mistakes; the official description above is the record.