Denial of service via authorization-header memory allocation
Published Sep 15, 2025 · Updated Sep 15, 2025
Resource exhaustion in Temporal Technologies Temporal Server allows remote attackers to interrupt affected OSS releases via authorization headers. The default JWT claim mapper applies insufficient bounds checking to an authorization header, permitting excessive memory allocation. Exploitation requires the default claim mapper and exposure to untrusted clients; Temporal Cloud is not affected.
Summary
What happened
Resource exhaustion in Temporal Technologies Temporal Server allows remote attackers to interrupt affected OSS releases via authorization headers. The default JWT claim mapper applies insufficient bounds checking to an authorization header, permitting excessive memory allocation. Exploitation requires the default claim mapper and exposure to untrusted clients; Temporal Cloud is not affected.
The record
- CVE
- CVE-2025-8396
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- Temporal Technologies
- Product
- Temporal Server
- Classifications
- CWE-770, CAPEC-130, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2025CVE publishedPublication date reported by the CVE source.
- Sep 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.26.3
- Affected versionversion=1.27.0 <1.27.3
- Affected versionversion=1.28.0 <1.28.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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