Authentication bypass via hard-coded JWT signing key
Published Dec 3, 2025 · Updated Dec 3, 2025
Hard-coded JWT key use in opsre go-ldap-admin 20251011 allows remote attackers to forge authentication tokens over the network. The Docker Compose configuration sets jwt.key to the literal value "secret key," which the JWT handler uses to sign and validate bearer tokens. No credentials or user interaction are required, but exploitation is complex; a forged token bypasses authorization and permits access to LDAP administration functions.
Summary
What happened
Hard-coded JWT key use in opsre go-ldap-admin 20251011 allows remote attackers to forge authentication tokens over the network. The Docker Compose configuration sets jwt.key to the literal value "secret key," which the JWT handler uses to sign and validate bearer tokens. No credentials or user interaction are required, but exploitation is complex; a forged token bypasses authorization and permits access to LDAP administration functions.
The record
- CVE
- CVE-2025-13948
- Published
- Dec 3, 2025
- Updated
- Dec 3, 2025
- Vendor
- opsre
- Product
- go-ldap-admin
- Classifications
- CWE-320, CWE-321, T1606
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 3, 2025CVE publishedPublication date reported by the CVE source.
- Dec 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=20251011
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- JWT signing-key proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo