[fix] SDKS-5037 - bump bcpkix-jdk18on to 1.84 to address CVE-2026-5588#201
[fix] SDKS-5037 - bump bcpkix-jdk18on to 1.84 to address CVE-2026-5588#201rodrigoareis wants to merge 2 commits into
Conversation
📝 WalkthroughWalkthroughThis PR adds ChangesBuild Configuration Maintenance
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #201 +/- ##
=============================================
- Coverage 44.46% 42.65% -1.82%
+ Complexity 1296 1287 -9
=============================================
Files 312 312
Lines 9447 9447
Branches 1403 1403
=============================================
- Hits 4201 4030 -171
- Misses 4649 4862 +213
+ Partials 597 555 -42
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CHANGELOG.md`:
- Line 3: Change the subheading level under the release header: replace the
incorrect "#### Fixed" heading with "### Fixed" so it correctly nests under the
"## [2.0.1]" release header and resolves the MD001 markdownlint error.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 181e7a7a-8763-49e8-bc8b-42d4dcde9024
📒 Files selected for processing (1)
CHANGELOG.md
| @@ -1,3 +1,8 @@ | |||
| ## [2.0.1] | |||
|
|
|||
| #### Fixed | |||
There was a problem hiding this comment.
Fix heading-level increment for markdownlint compliance.
At Line 3, #### Fixed skips a level under ## [2.0.1] and triggers MD001. Use ### Fixed instead.
Suggested patch
-#### Fixed
+### Fixed📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| #### Fixed | |
| ### Fixed |
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 3-3: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4
(MD001, heading-increment)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@CHANGELOG.md` at line 3, Change the subheading level under the release
header: replace the incorrect "#### Fixed" heading with "### Fixed" so it
correctly nests under the "## [2.0.1]" release header and resolves the MD001
markdownlint error.
JIRA Ticket
SDKS-5037 Vulnerability in android SDK 4.8.3 bcpkix-jdk18on version 1.81
Description
CVE-2026-5588 affects
org.bouncycastle:bcpkix-jdk18onat versions < 1.84.The catalog pin in
gradle/libs.versions.tomlis the single source of truthfor this dependency (no transitive consumer drags in a different version
and no resolutionStrategy.force entry exists for it), so a one-line bump
in the version catalog is sufficient.
The only production consumer of bcpkix-jdk18on in this repo is
mfa/binding's AppPinAuthenticator (X.509 v1 certificate constructionfor the APPLICATION_PIN device-binding flow). The Bouncy Castle PKIX
API surface used there has been stable across the 1.7x-1.8x line and
no source changes are required.
Verified:
940 actionable tasks)
configuration that references it.
Summary by CodeRabbit
Bug Fixes
Chores
Documentation