CVE-2024-35618: PingCAP TiDB v7.5.1 was discovered to contain a NULL pointer dereference via the component SortedRowContainer.

This month

HIGH 7.5REMOTEDOWNGRADE

CVE-2024-35618 is a high-severity flaw (CVSS 7.5) affecting tidb. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

PingCAP TiDB v7.5.1 was discovered to contain a NULL pointer dereference via the component SortedRowContainer.

Why this priority

High severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 65%)
CISA exploited list	No
Weakness	CWE-476
Published	2024-05-24
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: pingcap

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-05-24 15:15 UTCPublished CVE record published
2026-06-17 07:35 UTCUpdated Record last modified

pingcap tidb DOWNGRADE

Affected: 7.5.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 7.5.1

1. Check installed version

apt-cache policy tidb || rpm -q tidb || tidb --version

2. No fixed release: DOWNGRADE to a release before 7.5.1 (Debian / Ubuntu)

apt-cache madison tidb sudo apt install tidb=<VERSION_BEFORE_7.5.1> sudo apt-mark hold tidb

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list tidb sudo dnf downgrade tidb-<VERSION_BEFORE_7.5.1> sudo dnf versionlock add tidb

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-35618?

tidb: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-35618 being exploited?

CVE-2024-35618 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-35618 affect?

CVE-2024-35618 affects tidb. Severity is high (CVSS 7.5). PingCAP TiDB v7.5.1 was discovered to contain a NULL pointer dereference via the component SortedRowContainer.

How urgent is CVE-2024-35618?

Priority 40/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2024-41434 MEDIUM 4.3 DOWNGRADE PingCAP TiDB v8.1.0 was discovered to contain a buffer overflow via the component (*Column).GetDecimal
CVE-2024-41433 CRITICAL 9.8 DOWNGRADE PingCAP TiDB v8.1.0 was discovered to contain a buffer overflow via the component expression.ExplainExpression
CVE-2024-33809 MEDIUM 6.5 DOWNGRADE PingCAP TiDB v7.5.1 was discovered to contain a buffer overflow vulnerability, which could lead to database cr

References

← Back to latest CVEs