Skip to main content
MEDIUM

CVE-2023-45286

CVSS v3

5.9

MEDIUM

EPSS Score

0.7 %

exploit probability, as of 2026-10-19

CISA KEV

No

known exploited

Exploitation

—

SSVC status

Get an alert for each new CVE published for go-resty/resty.

Set up CVE WatchFree account · no credit card

Affected and fixed versions

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • github.com/go-resty/resty/v2Gofrom 2.10.0 · fixed in 2.11.0

Vendor advisories

  • CVE-2023-45286 Red Hat Product Security78 products fixed · 4 known affected

    go-resty: HTTP request body disclosure in github.com/go-resty/resty/v2

    mta/mta-hub-rhel9 as a component of Migration Toolkit for Applications 6 · mta/mta-windup-addon-rhel8 as a component of Migration Toolkit for Applications 6 · rhosdt/opentelemetry-rhel8-operator as a component of Red Hat OpenShift distributed tracing 2

  • RHSA-2024:3621 Red Hat Product Security76 products fixed

    Red Hat Security Advisory: Red Hat OpenShift distributed tracing 3.2.0 operator/operand containers update

  • RHSA-2024:3316 Red Hat Product Security2 products fixed

    Red Hat Security Advisory: Migration Toolkit for Applications security and bug fix update

Full record on NVD

Description

A race condition in go-resty can result in HTTP request body disclosure across requests. This condition can be triggered by calling sync.Pool.Put with the same *bytes.Buffer more than once, when request retries are enabled and a retry occurs. The call to sync.Pool.Get will then return a bytes.Buffer that hasn't had bytes.Buffer.Reset called on it. This dirty buffer will contain the HTTP request body from an unrelated request, and go-resty will append the current HTTP request body to it, sending two bodies in one request. The sync.Pool in question is defined at package level scope, so a completely unrelated server could receive the request body.

Technical details

Published
2023-11-28

Frequently asked questions

What is CVE-2023-45286?

A race condition in go-resty can result in HTTP request body disclosure across requests. This condition can be triggered by calling sync.Pool.Put with the same *bytes.Buffer more than once, when request retries are enabled and a retry occurs. The call to sync.Pool.Get will then return a bytes.Buffer that hasn't had bytes.Buffer.Reset called on it. This dirty buffer will contain the HTTP request body from an unrelated request, and go-resty will append the current HTTP request body to it, sending two bodies in one request. The sync.Pool in question is defined at package level scope, so a completely unrelated server could receive the request body.

Is CVE-2023-45286 actively exploited?

Active exploitation of CVE-2023-45286 has not been confirmed. Its EPSS score was 0.7% on 2026-10-19, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2023-45286?

CVE-2023-45286 has a CVSS v3 base score of 5.9 (MEDIUM severity).

Running go-resty/resty? Hear about its next vulnerability

CVE Watch matches each new CVE to the vendors and products you list (vendor and product, not the version) and puts it in your alerts with its KEV and EPSS status.

Get alerts for this productCISA KEV additions, October 2026Search CVEs

Already have an account? Open CVE WatchNo credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database