Application crash via unreclaimed native CBC ciphers
Published Aug 22, 2025 · Updated Oct 24, 2025
Uncontrolled resource consumption in Bouncy Castle for Java FIPS 2.1.0 and Java LTS 2.73.0 through 2.73.7 allows local users to crash applications. A non-static Disposer inner class in AESNativeCBC retains its enclosing cipher instance, so some garbage collectors do not reclaim native CBC ciphers after use. Repeated creation of native AES-CBC ciphers on any JVM exhausts the heap, raises OutOfMemoryError, and terminates the calling application.
Summary
What happened
Uncontrolled resource consumption in Bouncy Castle for Java FIPS 2.1.0 and Java LTS 2.73.0 through 2.73.7 allows local users to crash applications. A non-static Disposer inner class in AESNativeCBC retains its enclosing cipher instance, so some garbage collectors do not reclaim native CBC ciphers after use. Repeated creation of native AES-CBC ciphers on any JVM exhausts the heap, raises OutOfMemoryError, and terminates the calling application.
The record
- CVE
- CVE-2025-9341
- Published
- Aug 22, 2025
- Updated
- Oct 24, 2025
- Vendor
- Legion of the Bouncy Castle Inc.
- Product
- Bouncy Castle for Java FIPS
- Classifications
- CWE-400, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2025CVE publishedPublication date reported by the CVE source.
- Oct 24, 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=2.1.0
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