Improper Authentication Affecting telegraf-1.40 package, versions <1.40.0-r1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.5% (42nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-TELEGRAF140-19706355
  • published12 Sept 2026
  • disclosed10 Sept 2026

Introduced: 10 Sep 2026

NewCVE-2026-88018  (opens in a new tab)
CWE-287  (opens in a new tab)
CWE-306  (opens in a new tab)

How to fix?

Upgrade Chainguard telegraf-1.40 to version 1.40.0-r1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream telegraf-1.40 package and not the telegraf-1.40 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.75.1, rclone serve s3 configured with --auth-proxy but without --auth-key allows authPairMiddleware to register any client-chosen accessKeyID with an empty ws.s3Secret. gofakes3 then verifies the request’s SigV4 signature against that same empty secret, while Server.auth passes the access key identifier as both the user and authentication value to the proxy without an independent per-identity secret. An unauthenticated network attacker can therefore choose an arbitrary access key, sign with an empty secret, and reach whatever backend the auth-proxy script resolves for that identity. This issue is fixed in version 1.75.1.