Go SDK for CloudEvents's use of WithRoundTripper to create a Client leaks credentials

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2024-28110: 0.66% estimated exploitation activity in the next 30 days; percentile 51.69 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact What kind of vulnerability is it? Who is impacted? Using cloudevents.WithRoundTripper to create a cloudevents.Client with an authenticated http.RoundTripper causes the go-sdk to leak credentials to arbitrary endpoints. The relevant code is here (also inline, emphasis added): <preif p.Client == nil { p.Client = http.DefaultClient } if p.roundTripper != nil { p.Client.Transport = p.roundTripper } </pre When the transport is populated with an authenticated transport such as: - oauth2.Transport - idtoken.NewClient(...).Transport ... then http.DefaultClient is modified with the authenticated transport and will start to send Authorization tokens to any endpoint it is used to contact! Found and patched by: @tcnghia and @mattmoor Patches v.2.15.2

Published by the source

6 Mar 2024, 20:11 UTC

Last modified by the source

17 Feb 2026, 19:40 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5pf6-2qwx-pxm2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-28110

Advisory: Go SDK for CloudEvents's use of WithRoundTripper to create a Client leaks credentials
IDs: CVE-2024-28110, GHSA-5pf6-2qwx-pxm2
Record: https://patchnext.com/advisories/cve-2024-28110 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/cloudevents/sdk-go/v2 2.15.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cloudevents/sdk-go/v2: affected <= 2.15.1; fixed in 2.15.2

## Suggested inspection (read-only)
- Go github.com/cloudevents/sdk-go/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/cloudevents/sdk-go/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5pf6-2qwx-pxm2 (GitHub-reviewed advisory GHSA-5pf6-2qwx-pxm2 lists affected ranges: Go github.com/cloudevents/sdk-go/v2 >=0 <=2.15.1)

Commands are suggestions: review each one before running it.