checkNameConstraints
Defined in 2 files
Last patched
Overview
checkNameConstraints in bcgit/bc-java was changed by 2 published CVE fixes between 2025 and 2026, in 5 distinct patches that added or removed 240 lines in total.
Defined in 2 files
Last patched
checkNameConstraints in bcgit/bc-java was changed by 2 published CVE fixes between 2025 and 2026, in 5 distinct patches that added or removed 240 lines in total.
The name occurs in 2 files: pkix/src/main/java/org/bouncycastle/pkix/jcajce/PKIXCertPathReviewer.java, prov/src/main/java/org/bouncycastle/x509/PKIXCertPathReviewer.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 checkNameConstraints, newest first, with the lines each fix touched.
CVE-2026-71889 · pkix/src/main/java/org/bouncycastle/pkix/jcajce/PKIXCertPathReviewer.java · lines 455–569 · +21 −11 in 2 hunks
CVE-2026-71889 · prov/src/main/java/org/bouncycastle/x509/PKIXCertPathReviewer.java · lines 456–565 · +21 −11 in 2 hunks
CVE-2025-8916 · pkix/src/main/java/org/bouncycastle/pkix/jcajce/PKIXCertPathReviewer.java · lines 506–527 · +6 −81 in 2 hunks
CVE-2025-8916 · prov/src/main/java/org/bouncycastle/x509/PKIXCertPathReviewer.java · lines 506–530 · +7 −82 in 2 hunks
Get an alert when the next CVE fix lands in bcgit/bc-java, with the patched functions.
Monitor bc-java CVEsFunctions in bcgit/bc-java changed by the most CVE fixes.
Common questions about CVE fixes to checkNameConstraints.
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.