What is CVE-2023-45286?

CVE-2023-45286 is a medium-severity race condition vulnerability in github.com/go-resty/resty/v2 (go), affecting versions >= 2.10.0, < 2.11.0. It is fixed in 2.11.0. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.

How severe is CVE-2023-45286?

CVE-2023-45286 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/go-resty/resty/v2 are affected by CVE-2023-45286?

github.com/go-resty/resty/v2 (go) versions >= 2.10.0, < 2.11.0 is affected.

Is there a fix for CVE-2023-45286?

Yes. CVE-2023-45286 is fixed in 2.11.0. Upgrade to this version or later.

Is CVE-2023-45286 exploitable, and should I be worried?

Whether CVE-2023-45286 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-45286 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2023-45286 in github.com/go-resty/resty/v2

Q: How severe is CVE-2023-45286?

CVE-2023-45286 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/go-resty/resty/v2 are affected by CVE-2023-45286?

github.com/go-resty/resty/v2 (go) versions >= 2.10.0, < 2.11.0 is affected.

Q: Is there a fix for CVE-2023-45286?

Yes. CVE-2023-45286 is fixed in 2.11.0. Upgrade to this version or later.

Q: Is CVE-2023-45286 exploitable, and should I be worried?

Whether CVE-2023-45286 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2023-45286 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2023-45286?

Upgrade github.com/go-resty/resty/v2 to 2.11.0 or later.

Summary

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

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.

Impact

Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing. Typical impact: TOCTOU exploits, data corruption, or privilege escalation.

CVE-2023-45286 has a CVSS score of 5.9 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.11.0); upgrading removes the vulnerable code path.

Affected versions

github.com/go-resty/resty/v2 (>= 2.10.0, < 2.11.0)

Security releases

github.com/go-resty/resty/v2 → 2.11.0 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade github.com/go-resty/resty/v2 to 2.11.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2023-45286? CVE-2023-45286 is a medium-severity race condition vulnerability in github.com/go-resty/resty/v2 (go), affecting versions >= 2.10.0, < 2.11.0. It is fixed in 2.11.0. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.
How severe is CVE-2023-45286? CVE-2023-45286 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/go-resty/resty/v2 are affected by CVE-2023-45286? github.com/go-resty/resty/v2 (go) versions >= 2.10.0, < 2.11.0 is affected.
Is there a fix for CVE-2023-45286? Yes. CVE-2023-45286 is fixed in 2.11.0. Upgrade to this version or later.
Is CVE-2023-45286 exploitable, and should I be worried? Whether CVE-2023-45286 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-45286 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-45286? Upgrade github.com/go-resty/resty/v2 to 2.11.0 or later.