Redis subject to Integer Overflow leading to Remote Code Execution via Heap Overflow
Redis is an in-memory database that persists on disk. Versions 7.0.0 and above, prior to 7.0.5 are vulnerable to an Integer Overflow. Executing an `XAUTOCLAIM` command on a stream key in a specific state, with a specially crafted `COUNT` argument may cause an integer overflow, a subsequent heap overflow, and potentially lead to remote code execution. This has been patched in Redis version 7.0.5. No known workarounds exist.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2022-35951
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 6 Nov 2026, 04:19 UTC · Revision 1
Source evidence
Redis subject to Integer Overflow leading to Remote Code Execution via Heap Overflow
core-osv · Original sourcePublished 23 Sept 2022, 00:00 UTC
Redis is an in-memory database that persists on disk. Versions 7.0.0 and above, prior to 7.0.5 are vulnerable to an Integer Overflow. Executing an `XAUTOCLAIM` command on a stream key in a specific state, with a specially crafted `COUNT` argument may cause an integer overflow, a subsequent heap overflow, and potentially lead to remote code execution. This has been patched in Redis version 7.0.5. No known workarounds exist.
osv:CVE-2022-35951
Complete source record
{
"id": "b768fb5a49962fbcab68634180fb02fad44ee863e981489ed4fb239849d3dc97",
"url": "https://osv.dev/vulnerability/CVE-2022-35951",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Redis subject to Integer Overflow leading to Remote Code Execution via Heap Overflow",
"summary": "Redis is an in-memory database that persists on disk. Versions 7.0.0 and above, prior to 7.0.5 are vulnerable to an Integer Overflow. Executing an `XAUTOCLAIM` command on a stream key in a specific state, with a specially crafted `COUNT` argument may cause an integer overflow, a subsequent heap overflow, and potentially lead to remote code execution. This has been patched in Redis version 7.0.5. No known workarounds exist.",
"evidence": "osv:CVE-2022-35951",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2022-35951",
"aliases": [
"BIT-keydb-2022-35951",
"BIT-redis-2022-35951",
"BIT-valkey-2022-35951",
"CVE-2022-35951",
"GHSA-5gc4-76rx-22c9"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/redis/redis",
"type": "GIT",
"events": [
{
"introduced": "d375595d5e3ae2e5c29e6c00a2dc3d60578fd9fc"
},
{
"fixed": "1571907ea02020a829fca63806780c6f3ecf65a0"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "7.0.0"
},
{
"fixed": "7.0.5"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"cpe": "cpe:2.3:a:redis:redis:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "7.0.0"
},
{
"fixed": "7.0.5"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"7.0.4",
"7.0.3",
"7.0.2",
"7.0.1",
"7.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-35951.json"
}
}
],
"modified": "2026-10-28T02:30:46.694182812Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/35xxx/CVE-2022-35951.json",
"https://github.com/redis/redis/security/advisories/GHSA-5gc4-76rx-22c9",
"https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/A7INCOOFPPEAKNDBZU3TIZJPYXBULI2C/",
"https://nvd.nist.gov/vuln/detail/CVE-2022-35951",
"https://security.gentoo.org/glsa/202209-17",
"https://security.netapp.com/advisory/ntap-20221020-0005/"
],
"provider_metadata": {
"cwe_ids": [
"CWE-190"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/35xxx/CVE-2022-35951.json"
}
},
"related_cves": [
{
"value": "CVE-2022-35951",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 514598,
"published_at": "2022-09-23T00:00:00+00:00"
}