Integer Overflow to Buffer Overflow Affecting sqlx package, versions <0.8.6-r3
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-SQLX-15231393
- published6 Feb 2026
- disclosed4 Feb 2026
Introduced: 4 Feb 2026
NewCVE-2026-25541 (opens in a new tab)How to fix?
Upgrade Chainguard sqlx to version 0.8.6-r3 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream sqlx package and not the sqlx package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
Bytes is a utility library for working with bytes. From version 1.2.1 to before 1.11.1, Bytes is vulnerable to integer overflow in BytesMut::reserve. In the unique reclaim path of BytesMut::reserve, if the condition "v_capacity >= new_cap + offset" uses an unchecked addition. When new_cap + offset overflows usize in release builds, this condition may incorrectly pass, causing self.cap to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as spare_capacity_mut() then trust this corrupted cap value and may create out-of-bounds slices, leading to UB. This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks. This issue has been patched in version 1.11.1.