# CVE-2025-23386: gerbera: Privilege escalation from user gerbera to root because of insecure %post script

> A local attacker with gerbera user privileges can escalate to root due to insecure permissions in the package post-installation script.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 10 Apr 2025
- **Updated:** 10 Apr 2025
- **Also known as:** GHSA-jrg3-gh37-h96x, UBUNTU-CVE-2025-23386, openSUSE-SU-2025:14864-1

## What is CVE-2025-23386?

CVE-2025-23386 is a high-severity vulnerability in openSUSE Tumbleweed, published on 10 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Incorrect Default Permissions vulnerability in the openSUSE Tumbleweed package gerbera allows the service user gerbera to escalate to root.,This issue affects gerbera on openSUSE Tumbleweed before 2.5.0-1.1.

Weakness: CWE-276 (Incorrect Default Permissions)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gerbera` | openSUSE:Tumbleweed | All versions | 2.5.0-1.1 |

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

Upgrade to a fixed version.

## Is CVE-2025-23386 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-23386 is a high-severity vulnerability in openSUSE Tumbleweed, published on 10 Apr 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-23386 in the wild and no public exploit code.

Affected product: openSUSE Tumbleweed. 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-23386/ (Markdown: https://insights.sbomify.com/CVE-2025-23386/index.md)
```

## Sources

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

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