chore: Create CVE troubleshooting guide#2456
Merged
Merged
Conversation
davidkna-sap
reviewed
May 8, 2026
marikaner
commented
May 8, 2026
davidkna-sap
reviewed
May 8, 2026
Co-authored-by: David Knaack <david.knaack@sap.com>
marikaner
commented
May 8, 2026
marikaner
commented
May 8, 2026
davidkna-sap
requested changes
May 11, 2026
marikaner
commented
May 19, 2026
marikaner
commented
May 19, 2026
Co-authored-by: David Knaack <david.knaack@sap.com> Co-authored-by: Marika Marszalkowski <marika.marszalkowski@sap.com>
marikaner
commented
May 19, 2026
Co-authored-by: Marika Marszalkowski <marika.marszalkowski@sap.com>
Co-authored-by: David Knaack <david.knaack@sap.com>
davidkna-sap
approved these changes
May 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I created a guide on what to do in case users encounter a CVE from a Cloud SDK dependency. I have the impression this is coming up more often now and users sometimes start to panic and ask us to fix the vulnerability, while they are able to fix it on their own. This should hopefully make it easier for us to guide them towards a solution and them to understand the steps that are needed.