Redis 2.6.0 Release Candidate 1

Submit a proposal Propose CVE/GCVE/GHSA reference

Approved changes feed: RSS · Atom

cpe:2.3:a:redis:redis:2.6.0:rc1:*:*:*:*:*:*

part: a version: 2.6.0 update: rc1

VendorRedis (6c818399-7e28-57a6-8fa0-307b3f9a96f5)
ProductRedis (56983391-c965-509a-bb47-f44d8ba59efe)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:deb/debian/redis purl2cpe 2026-06-01 10:11:34.098144
pkg:deb/ubuntu/redis purl2cpe 2026-06-01 10:11:34.098146
pkg:docker/redis purl2cpe 2026-06-01 10:11:34.098148
pkg:github/redis/redis purl2cpe 2026-06-01 10:11:34.098149
pkg:rpm/centos/redis purl2cpe 2026-06-01 10:11:34.098161
pkg:rpm/opensuse/redis purl2cpe 2026-06-01 10:11:34.098163

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-45145 vulnerable 2026-06-08 06:12:42.050816 Redis Unix-domain socket may have be exposed with the wrong permissions for a short time window.
LOW (3.6)
Redis is an in-memory database that persists on disk. On startup, Redis begins listening on a Unix socket before adjusting its permissions to the user-provided configuration. If a permissive umask(2) is used, this creates a race condition that enables, during a short period of time, another process to establish an otherwise unauthorized connection. This problem has existed since Redis 2.6.0-RC1. This issue has been addressed in Redis versions 7.2.2, 7.0.14 and 6.2.14. Users are advised to upgrade. For users unable to upgrade, it is possible to work around the problem by disabling Unix sockets, starting Redis with a restrictive umask, or storing the Unix socket file in a protected directory.
Published: 2023-10-18T20:17:08.588Z
Updated: 2025-02-13T17:13:50.793Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.