Unauthenticated service crash via TLS connection leak
Published Jul 23, 2026 · Updated Jul 23, 2026
Resource exhaustion in Red Hat Certificate System 9 allows remote attackers to crash its Java process through repeated HTTPS requests. The published record identifies a TLS-connection memory leak but does not disclose the exact object, allocation site, or failed release operation. No authentication is required, and some server configurations require manual intervention after memory exhaustion terminates the process.
Summary
What happened
Resource exhaustion in Red Hat Certificate System 9 allows remote attackers to crash its Java process through repeated HTTPS requests. The published record identifies a TLS-connection memory leak but does not disclose the exact object, allocation site, or failed release operation. No authentication is required, and some server configurations require manual intervention after memory exhaustion terminates the process.
The record
- CVE
- CVE-2026-12353
- Published
- Jul 23, 2026
- Updated
- Jul 23, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Certificate System
- Classifications
- CWE-772, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 23, 2026CVE publishedPublication date reported by the CVE source.
- Jul 23, 2026Record 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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