← Back
CVE-2025-8916
Vulnerability in org.bouncycastle:bcpkix-fips (CVE-2025-8916)
Summary
vulnerability in org.bouncycastle:bcpkix-fips (CVE-2025-8916). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.0.8` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-8916** has been found in org.bouncycastle:bcpkix-fips.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade org.bouncycastle:bcpkix-fips to **2.0.8** or later.
If unsure, ask your IT team or search "org.bouncycastle:bcpkix-fips CVE-2025-8916" on the vendor's site.
CVE-2025-8916 (org.bouncycastle:bcpkix-fips) — CWE-770 /
Patched: `2.0.8` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-770) exists in org.bouncycastle:bcpkix-fips.
📍 Affected scope
org.bouncycastle:bcpkix-fips — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.0.8**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.bouncycastle:bcpkix-fips' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'org.bouncycastle:bcpkix-fips' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.bouncycastle:bcpkix-fips` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade org.bouncycastle:bcpkix-fips to 2.0.8ステージング環境で 2.0.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.bouncycastle:bcpkix-fips
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.8"}]}]
maven
org.bouncycastle:bcpkix-jdk15on
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.79"}]}]
maven
org.bouncycastle:bcpkix-jdk15to18
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.79"}]}]
maven
org.bouncycastle:bcpkix-jdk18on
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.79"}]}]
References
- web https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902025%E2%80%908916
- web https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- web https://nvd.nist.gov/vuln/detail/CVE-2025-8916
- web https://github.com/bcgit/bc-java/commit/310b30a4fbf36d13f6cc201ffa7771715641e67e
- web https://github.com/bcgit/bc-java/commit/ff444a479942d88de64004dc82c3ee32a9e9075a
- web https://github.com/advisories/GHSA-4cx2-fc23-5wg6