GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — [Snyk] Security upgrade io.kubernetes:client-java from 17.0.2 to 22.0.1-legacy by caniszczyk · Pull Request #19 · OpenFunction/java-samples

Conversation

@caniszczyk

@caniszczyk caniszczyk commented Aug 5, 2026

Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to fix 6 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

  • pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue Score Upgrade
critical severity Improper Certificate Validation
SNYK-JAVA-ORGBOUNCYCASTLE-18519194		   751   io.kubernetes:client-java:
17.0.2 -> 22.0.1-legacy
No Known Exploit
high severity Uncontrolled Recursion
SNYK-JAVA-ORGBOUNCYCASTLE-18519010		   721   io.kubernetes:client-java:
17.0.2 -> 22.0.1-legacy
No Known Exploit
high severity Improper Validation of Integrity Check Value
SNYK-JAVA-ORGBOUNCYCASTLE-18519127		   721   io.kubernetes:client-java:
17.0.2 -> 22.0.1-legacy
No Known Exploit
high severity Improper Validation of Integrity Check Value
SNYK-JAVA-ORGBOUNCYCASTLE-18519148		   721   io.kubernetes:client-java:
17.0.2 -> 22.0.1-legacy
No Known Exploit
high severity Improper Validation of Integrity Check Value
SNYK-JAVA-ORGBOUNCYCASTLE-18519163		   721   io.kubernetes:client-java:
17.0.2 -> 22.0.1-legacy
No Known Exploit
high severity Memory Allocation with Excessive Size Value
SNYK-JAVA-ORGBOUNCYCASTLE-18519180		   721   io.kubernetes:client-java:
17.0.2 -> 22.0.1-legacy
No Known Exploit

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Uncontrolled Recursion

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@snyk-bot
fix: pom.xml to reduce vulnerabilities
753b79a 
The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-18519194
- https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-18519010
- https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-18519127
- https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-18519148
- https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-18519163
- https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-18519180
@caniszczyk

caniszczyk commented Aug 5, 2026

Copy link
Copy Markdown
Author

Merge Risk: High

This is a major version upgrade across five major versions, from 17.0.2 to 22.0.1-legacy. This introduces significant breaking changes and risks that require careful validation.

Key Breaking Changes & Risks:

  • Kubernetes API Model Changes: Each major version of this library corresponds to a new Kubernetes API version. This upgrade spans from Kubernetes ~1.25 (for client v17) to 1.31 (for client v22). APIs deprecated or removed in these Kubernetes versions will cause breaking changes in the application code. Code must be updated to use the newer, stable API resource versions.
  • Java Version Incompatibility Risk: The -legacy suffix is intended to provide an artifact that retains the older API style and, crucially, supports Java 8. However, a bug was reported for v22.0.0-legacy where it was incorrectly compiled with a Java 11 requirement. It is not confirmed if this is fixed in 22.0.1-legacy. This poses a significant risk if the target environment is Java 8.
  • API Behavior Changes: Starting with v20.0.0, the non-legacy client introduced major API refactoring, such as consolidating optional parameters into a single options object. While the legacy artifact avoids this specific refactoring, the underlying code has still changed significantly across five major versions.

Recommendation:

  1. Verify Java Version: Before merging, confirm that the 22.0.1-legacy artifact is compatible with your project's target Java version (especially if it is Java 8).
  2. Audit Kubernetes API Usage: Review all code that interacts with the Kubernetes API. Identify and update any usage of deprecated or removed API versions that occurred between Kubernetes 1.25 and 1.31.
  3. Thorough Testing: Due to the scale of this upgrade, extensive testing is required to validate application behavior against a target Kubernetes cluster.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@CLAassistant

CLAassistant commented Sep 5, 2026

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

3 participants

@caniszczyk @CLAassistant @snyk-bot
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.