# CVE-2025-13948: opsre go-ldap-admin JWT docker-compose.yaml hard-coded key

> Attackers can exploit a hard-coded JWT secret key in the docker-compose configuration to bypass authentication in the go-ldap-admin application.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Dec 2025
- **Updated:** 3 Dec 2025
- **Also known as:** GHSA-m3vx-qqqj-j2c4

## What is CVE-2025-13948?

CVE-2025-13948 is a medium-severity vulnerability in opsre go-ldap-admin, published on 3 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was determined in opsre go-ldap-admin up to 20251011. This issue affects some unknown processing of the file docs/docker-compose/docker-compose.yaml of the component JWT Handler. Executing manipulation of the argument secret key can lead to use of hard-coded cryptographic key
 . The attack can be launched remotely. Attacks of this nature are highly complex. The exploitability is assessed as difficult. The exploit has been publicly disclosed and may be utilized.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key), CWE-320

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


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

No fix has been published for CVE-2025-13948 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-13948 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13948 is a medium-severity vulnerability in opsre go-ldap-admin, published on 3 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13948 in the wild and no public exploit code.

Affected product: opsre go-ldap-admin. 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-13948/ (Markdown: https://insights.sbomify.com/CVE-2025-13948/index.md)
```

## Sources

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

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