Skip to content

chore: Bump org.bouncycastle:bcprov-jdk18on 1.84 -> 1.85 for CVE-2026-59638. - #299

Merged
TheSnoozer merged 1 commit into
git-commit-id:masterfrom
craftmaster2190:bump-org.bouncycastle-bcprov-jdk18on-for-CVE-2026-59638
Aug 15, 2026
Merged

chore: Bump org.bouncycastle:bcprov-jdk18on 1.84 -> 1.85 for CVE-2026-59638.#299
TheSnoozer merged 1 commit into
git-commit-id:masterfrom
craftmaster2190:bump-org.bouncycastle-bcprov-jdk18on-for-CVE-2026-59638

Conversation

@craftmaster2190

Copy link
Copy Markdown
Contributor

https://www.cve.org/CVERecord?id=CVE-2026-59638

Contributor Checklist

  • Added relevant integration or unit tests to verify the changes
  • Update the Readme or any other documentation (including relevant Javadoc)
  • Ensured that tests pass locally: mvn clean package
  • Ensured that the code meets the current checkstyle coding style definition: mvn clean verify -Pcheckstyle -Dmaven.test.skip=true -B

@edwardsre

Copy link
Copy Markdown

We are using the git-commit-id-maven-plugin:9.2.0 via Spring Boot 4.1.0. That plugin version is using bouncy castle version 1.81.

@TheSnoozer
TheSnoozer merged commit 4c42eba into git-commit-id:master Aug 15, 2026
18 checks passed
@TheSnoozer

Copy link
Copy Markdown
Contributor

Thanks for the PR, not sure how and if the plugin is even affected by this as the plugin usually operates on the offline git resources (and thus does not even would trigger some validate of some hostname information).
Anyways shouldn't hurt.
Do you need a release to make some CVE check pipeline green again?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants