Skip to content

chore: Create CVE troubleshooting guide#2456

Open
marikaner wants to merge 7 commits into
mainfrom
troubleshooting
Open

chore: Create CVE troubleshooting guide#2456
marikaner wants to merge 7 commits into
mainfrom
troubleshooting

Conversation

@marikaner
Copy link
Copy Markdown
Contributor

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.


If the fixed version falls within the SDK's declared semver range (i.e., no major version bump), you can update the vulnerable package in your own project:

```
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[pp] pnpm will sometimes require pnpm update --recursive <package-name>

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we add instructions on other package managers than npm? I was thinking that if you use pnpm you probably don't need this guide. Also, AFAIK we only have instructions for npm everywhere else.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's fair, but pnpm is actually notable here because for us dependabot routinely fails to handle security remediation PRs.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will add it then.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as discussed, we will ultimately not add it.

Comment thread docs-js/troubleshooting.mdx Outdated
Comment thread docs-js/troubleshooting.mdx Outdated
Co-authored-by: David Knaack <david.knaack@sap.com>
Comment thread docs-js/troubleshooting.mdx Outdated
Comment thread docs-js/troubleshooting.mdx Outdated
@marikaner marikaner requested a review from davidkna-sap May 11, 2026 10:10
```

:::note
Be aware of the [`min-release-age`](https://docs.npmjs.com/cli/v10/using-npm/config#min-release-age) setting in both directions:
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[req] This was added in v11:

Suggested change
Be aware of the [`min-release-age`](https://docs.npmjs.com/cli/v10/using-npm/config#min-release-age) setting in both directions:
Be aware of the [`min-release-age`](https://docs.npmjs.com/cli/v11/using-npm/config#min-release-age) setting in both directions:

If the fixed version falls within the SDK's declared semver range (i.e., no major version bump), update the vulnerable package:

```
npm update PACKAGE_NAME
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[req] Both npm update and npm audit appear to respect min-release-age during dependency resolution.

Suggested change
npm update PACKAGE_NAME
npm update --min-release-age=0 PACKAGE_NAME

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.

2 participants