[Snyk] Security upgrade golang from 1.21 to 1.26rc2

[Dustin4444]

Snyk has created this PR to fix 3 vulnerabilities in the dockerfile dependencies of this project.

Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

Snyk changed the following file(s):

• telegraf-build/scripts/Dockerfile

We recommend upgrading to golang:1.26rc2, as this image has only 119 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Link Following SNYK-DEBIAN12-GIT-6846203	821
	Link Following SNYK-DEBIAN12-GIT-6846203	821
	Arbitrary Code Injection SNYK-DEBIAN12-GIT-5461954	721
	Arbitrary Code Injection SNYK-DEBIAN12-GIT-5461954	721
	Integer Overflow or Wraparound SNYK-DEBIAN12-EXPAT-7855502	714

---

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:

🦉 Integer Overflow or Wraparound

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snyk-fix-5f00239c188993b40321c03269ba858a

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @Dustin4444, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, focuses on enhancing the project's security by updating the base Go image within the Dockerfile. The primary goal is to mitigate several known vulnerabilities by moving to a more recent Go version, thereby ensuring the application benefits from the latest security patches and a reduced attack surface.

Highlights

• Dependency Upgrade: The golang base image in telegraf-build/scripts/Dockerfile has been upgraded from version 1.21 to 1.26rc2.
• Security Fixes: This upgrade addresses 3 identified vulnerabilities, including critical and high severity issues such as Link Following and Arbitrary Code Injection, improving the project's security posture.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, aims to fix security vulnerabilities by upgrading the Go version in the Dockerfile from 1.21 to 1.26rc2. While the intention to upgrade is good, the chosen version 1.26rc2 is a release candidate for a future Go version, which is not suitable for a stable build environment. My review includes a critical comment suggesting to use the latest stable Go version, 1.22, instead to ensure build reliability and stability.

[gemini-code-assist]

While upgrading Go to fix security vulnerabilities is a good practice, using a release candidate (RC) version like 1.26rc2 for a base image is highly discouraged for production or release builds. RC versions are not stable and may contain bugs. Furthermore, 1.26 is a future version of Go, making this tag particularly risky and potentially non-existent. It is recommended to use the latest stable version of Go. I suggest using golang:1.22 which is the latest stable release series.

FROM golang:1.22