Security Resilience

CVE-2025-13948

Exposed Creds

Published
03 December 2025
Modified
18 October 2026
CVSS Score v4 2.9
Click a component to see what it means
Raw vectorCVSS: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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0030 21th percentile
Risk Priority 24 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-13948 is a low-severity Use of Hard-coded Cryptographic Key (CWE-321) vulnerability. Its CVSS base score is 2.9 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

. 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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
T1552.004 Private Keys Credential Access
Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-12615Shared CWE-320, CWE-321
CVE-2026-5471Shared CWE-320, CWE-321
CVE-2026-5457Shared CWE-320, CWE-321
CVE-2025-15005Shared CWE-320, CWE-321
CVE-2026-5455Shared CWE-320, CWE-321
CVE-2026-105392Shared CWE-320, CWE-321
CVE-2025-13877Shared CWE-320, CWE-321
CVE-2025-14651Shared CWE-320, CWE-321
CVE-2026-4588Shared CWE-320, CWE-321
CVE-2026-6611Shared CWE-320, CWE-321

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Requiring cryptographic keys to be established and managed according to defined requirements prevents developers from embedding static unchangeable keys.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure-SDLC activities such as code review and secret scanning directly prevent embedding static keys.

PR.DS-01 partial match
blocks

Data-at-rest protection policies require proper key management and therefore discourage hard-coded keys.

PR.DS-02 partial match
blocks

Data-in-transit protection similarly depends on non-hard-coded keys for encryption.

PR.PS-01 partial match
blocks

Configuration baselines and reviews can prohibit hard-coded keys in deployed artifacts.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

Key-management controls that govern generation, rotation and protection of keys make the use of embedded hard-coded cryptographic keys less likely and easier to detect.

References