Defined in 2 files
Last patched
calculateAgreement in bcgit/bc-java was changed by 2 published CVE fixes between 2018 and 2026, in 3 distinct patches that added or removed 31 lines in total.
The name occurs in 2 files: core/src/main/java/org/bouncycastle/crypto/agreement/DHAgreement.java, core/src/main/java/org/bouncycastle/crypto/agreement/DHBasicAgreement.java.
bcgit/bc-java has 73 CVEs with a located fix in total, so 3% of them touched this function.
Every published CVE whose fix changed calculateAgreement, newest first, with the lines each fix touched.
CVE-2026-59650 · core/src/main/java/org/bouncycastle/crypto/agreement/DHAgreement.java · lines 86–123 · +11 −4 in 2 hunks
CVE-2016-1000346 · core/src/main/java/org/bouncycastle/crypto/agreement/DHAgreement.java · lines 94–100 · +7 −1
CVE-2016-1000346 · core/src/main/java/org/bouncycastle/crypto/agreement/DHBasicAgreement.java · lines 71–77 · +7 −1
Get an alert when the next CVE fix lands in bcgit/bc-java, with the patched functions.
Monitor bc-java CVEsFunctions in the same files that CVE fixes also changed.
Functions in bcgit/bc-java changed by the most CVE fixes.
Common questions about CVE fixes to calculateAgreement.
Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.
Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.
