Strip VCS build information from go builds #61502
Open
Conversation
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
Scanners such as trivy are misinterpreting the go pseudoversions describing which commit was used to build the project. See: aquasecurity/trivy#9446 This causes false positives and considerable toil for our support team as every user/customer is seeing trivy reporting that Teleport is affected by CVE-2022-36633 (it is not). Trivy doesn't seem to want to fix their tool so we must strip VCS information from the go binary to stop the false positives. This actually makes the binaries _less traceable_, but this is the only workaround to reduce the noise caused by those tools.
zmb3
approved these changes
Nov 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Scanners such as trivy are misinterpreting the go pseudoversions describing which commit was used to build the project. See: aquasecurity/trivy#9446
This causes false positives and considerable toil for our support team as every user/customer is seeing that Teleport is affected by CVE-2022-36633 (it is not).
Trivy devs don't seem to want to fix this so we must strip VCS information from the go binary to stop the false positives.
This actually makes the binaries less traceable, but this is the only workaround to reduce the noise caused by those tools.
Changelog: Prevented Trivy from reporting false positives when scanning the Teleport binaries.