Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2026-13505— Zeroisation of sensitive key material on garbage collection relies on finalization

CVSS 8.7 · High EPSS 0.25% · P17

Possible ATT&CK Techniques 1AI

T1530 · Data from Cloud Storage

Affected Version Matrix 3

VendorProductVersion RangeStatus
Legion of the Bouncy Castle Inc.BC-FJA1.0.0< 1.0.2.7affected
2.0.0< 2.0.2affected
2.1.0< 2.1.3affected
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2026-13505

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Zeroisation of sensitive key material on garbage collection relies on finalization
Source: CVE Program / CVE List V5
Vulnerability Description
In Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 (2.0.X series) and 2.1.3 (2.1.X series), sensitive key material held by the AES and DESede engines, the SP 800-90A DRBGs, SymmetricSecretKey and the PBKD and scrypt parameter classes was zeroised on garbage collection by overriding Object.finalize. Finalization runs at an unspecified time and in an unspecified order and is serviced by a single finalizer thread, so where objects carrying a finalizer are allocated faster than that thread retires them the pending-finalization queue grows without bound: disposal falls arbitrarily far behind, which can contribute to an OutOfMemoryError under load, and the key material those objects hold stays resident in the heap for as long as they are queued, defeating the purpose of the zeroisation. The behaviour was not a problem on Java 8 or Java 11; it is later JVMs, on which finalization has been deprecated and progressively de-emphasised, where it becomes one. Disposal of these classes now runs from a java.lang.ref.Cleaner registered in the multi-release jdk1.9 overlay, so on Java 9 and later it no longer depends on the finalizer being scheduled. Bouncy Castle for Java (bcprov) and Bouncy Castle for Java LTS are not affected, as neither implements the finalizer-based zeroisation scheme.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/U:Amber
Source: CVE Program / CVE List V5
Vulnerability Type
对已超过有效生命周期的资源丧失索引
Source: CVE Program / CVE List V5
Vulnerability Title
Legion of the Bouncy Castle Inc BC-FJA 资源管理错误漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Legion of the Bouncy Castle Inc BC-FJA是Legion of the Bouncy Castle Inc组织的一款Java加密库。 Legion of the Bouncy Castle Inc BC-FJA 1.0.2.7版本之前的1.0.X版本、2.0.2版本之前的2.0.X版本和2.1.3版本之前的2.1.X版本存在资源管理错误漏洞,该漏洞源于通过覆盖Object.finalize在垃圾回收时对AES和DESede引擎等持有的敏感密钥材料进行零化处理,由于fina
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
Legion of the Bouncy Castle Inc.BC-FJA 1.0.0 ~ 1.0.2.7 -

II. Public POCs for CVE-2026-13505

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-13505

登录查看更多情报信息。

Proof of Concept for CVE-2026-13505 (1)

IV. Related Vulnerabilities

V. Comments for CVE-2026-13505

No comments yet


Leave a comment