dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2026-24814

CRITICAL · 10.0 CVSS v4.0 Published 2026-01-27
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Integer Overflow or Wraparound vulnerability in swoole swoole-src (thirdparty/hiredis modules). This vulnerability is associated with program files sds.C. This issue affects swoole-src: before 6.0.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence

Integer overflow or wraparound vulnerability in the sds.c file within the thirdparty/hiredis module of swoole-src. The vulnerability could allow memory corruption leading to potential remote code execution, as indicated by the critical CVSS score of 10.

MitigationUpgrade swoole-src to version 6.0.2 or later to patch the integer overflow vulnerability in the thirdparty/hiredis sds.c module.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
Y
User interaction
None
Scope
N

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:Y/R:U/V:C/RE:L/U:Red

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if swoole-src is installed
    Run `php -m | grep swoole` to see if swoole is loaded as a PHP extension, or check for swoole installation via package manager or composer
    Affected if swoole is not installed - not affected; if installed, proceed to next check
  2. Determine the installed swoole-src version
    Run `php -r 'echo phpversion("swoole");'` or check via `swoole_version()` function in PHP, or inspect the extension file metadata
    Affected if Unable to determine version - manual inspection required; if version is >= 6.0.2, not affected; if version < 6.0.2, potentially affected
  3. Verify the thirdparty/hiredis module is compiled into swoole
    Check the swoole extension for linked hiredis by running `php -i | grep -i hiredis` or examining the swoole source/extension directory for thirdparty/hiredis presence
    Affected if hiredis module not present in swoole installation - may not be affected; if hiredis is present, proceed to next check
  4. Confirm version is within affected range
    Compare the installed version from step 2 against the fixed version 6.0.2. Any version below 6.0.2 contains the vulnerable integer overflow in thirdparty/hiredis sds.c
    Affected if Installed version is below 6.0.2 - affected by CVE-2026-24814

User is affected if swoole-src is installed with a version lower than 6.0.2 and the thirdparty/hiredis module is compiled into the swoole extension.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade swoole-src to version 6.0.2 or later to patch the integer overflow vulnerability in the thirdparty/hiredis sds.c module.

Recommended fix High confidence

6.0.2

  1. Check the currently installed swoole version using 'php -m | grep swoole' or 'composer show swoole/swoole-src'.
  2. Upgrade swoole-src to version 6.0.2 or later. For Composer: 'composer require swoole/swoole-src:^6.0.2 --update-with-dependencies'. For PECL: 'pecl upgrade swoole'. For source compilation, download the release from https://github.com/swoole/swoole-src/releases and compile.
  3. Verify the new version by running the command from step 1 and confirming it shows 6.0.2 or newer.
  4. Restart any PHP processes (e.g., PHP-FPM, Apache, or other long-running processes) to load the updated extension: 'systemctl restart php-fpm' or appropriate service restart.
  5. Test your application to ensure functionality remains intact after the upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24814 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24814 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data