CVE-2023-26154

MEDIUM
5.9
CVSS Score
Published: December 6, 2023 at 05:00 AM UTC
Updated: June 17, 2026 at 05:42 AM UTC
5 products affected across 1 vendorSwiftC CorePubnub

Using pubnub by N/A?

Get instant alerts when new vulnerabilities affect pubnub - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.9
Exploit prediction
EPSS 1.0%

Description

Versions of the package pubnub before 7.4.0; all versions of the package com.pubnub:pubnub; versions of the package pubnub before 6.19.0; all versions of the package github.com/pubnub/go; versions of the package github.com/pubnub/go/v7 before 7.2.0; versions of the package pubnub before 7.3.0; versions of the package pubnub/pubnub before 6.1.0; versions of the package pubnub before 5.3.0; versions of the package pubnub before 0.4.0; versions of the package pubnub/c-core before 4.5.0; versions of the package com.pubnub:pubnub-kotlin before 7.7.0; versions of the package pubnub/swift before 6.2.0; versions of the package pubnub before 5.2.0; versions of the package pubnub before 4.3.0 are vulnerable to Insufficient Entropy via the getKey function, due to inefficient implementation of the AES-256-CBC cryptographic algorithm. The provided encrypt function is less secure when hex encoding and trimming are applied, leaving half of the bits in the key always the same for every encoded message or file. **Note:** In order to exploit this vulnerability, the attacker needs to invest resources in preparing the attack and brute-force the encryption.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 4.5.0
Affected range stops below 4.5.0, so it looks safe — our inference, not a vendor statement
v < 7.7.0
Affected range stops below 7.7.0, so it looks safe — our inference, not a vendor statement
v < 0.4.0v < 4.3.0v < 4.5.0v < 5.2.0v < 5.3.0v < 6.1.0v < 6.19.0v < 7.2.0v < 7.3.0v < 7.4.03.6.4 ≤ v < 4.3.04.3.1 ≤ v < 5.2.06.0.0 ≤ v < 6.1.06.2.0 ≤ v < 6.19.07.0.0 ≤ v < 7.3.07.3.1 ≤ v < 7.4.0
Affected range stops below 0.4.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.3.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.5.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.2.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.3.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.19.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.2.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.3.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.4.0, so it looks safe — our inference, not a vendor statement
v < 6.2.0
Affected range stops below 6.2.0, so it looks safe — our inference, not a vendor statement
v < 7.2.0
Affected range stops below 7.2.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

5.9MEDIUMsnyk
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-331

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card