Unauthenticated service hang via bearer-token misbinding
Published Dec 15, 2025 · Updated Dec 15, 2025
Uncontrolled resource consumption in Wekan 8.15 and earlier allows remote attackers to hang the server through attachment uploads. The attachment upload API mistakes the Authorization bearer value for a user ID and enters a request-body branch that never completes. Any non-empty bearer token reaches the branch without authentication, allowing concurrent malformed requests to exhaust connections; absent token validation also exposes identity spoofing.
Summary
What happened
Uncontrolled resource consumption in Wekan 8.15 and earlier allows remote attackers to hang the server through attachment uploads. The attachment upload API mistakes the Authorization bearer value for a user ID and enters a request-body branch that never completes. Any non-empty bearer token reaches the branch without authentication, allowing concurrent malformed requests to exhaust connections; absent token validation also exposes identity spoofing.
The record
- CVE
- CVE-2025-65781
- Published
- Dec 15, 2025
- Updated
- Dec 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, CWE-287, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 15, 2025CVE publishedPublication date reported by the CVE source.
- Dec 15, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
No public exploit references are available in this record.
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