CVE-2024-24213: Supabase PostgreSQL v15.1 was discovered to contain a SQL injection vulnerability via the component /pg_meta/d

This month

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2024-24213 is a critical-severity flaw (CVSS 9.8) affecting postgres. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Supabase PostgreSQL v15.1 was discovered to contain a SQL injection vulnerability via the component /pg_meta/default/query. NOTE: the vendor's position is that this is an intended feature; also, it exists in the Supabase dashboard product, not the Supabase PostgreSQL product. Specifically, /pg_meta/default/query is for SQL queries that are entered in an intended UI by an authorized user. Nothing is injected.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

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

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.1% (top 35%)
CISA exploited list	No
Weakness	CWE-89
Published	2024-02-08
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: supabase

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

Am I affected?

Timeline

2024-02-08 18:15 UTCPublished CVE record published
2026-06-17 07:14 UTCUpdated Record last modified

supabase postgres DOWNGRADE

Affected: 15.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 15.1

1. Check installed version

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

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

apt-cache madison postgres sudo apt install postgres=<VERSION_BEFORE_15.1> sudo apt-mark hold postgres

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

dnf --showduplicates list postgres sudo dnf downgrade postgres-<VERSION_BEFORE_15.1> sudo dnf versionlock add postgres

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-24213?

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

Is CVE-2024-24213 being exploited?

CVE-2024-24213 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-24213 affect?

CVE-2024-24213 affects postgres. Severity is critical (CVSS 9.8). Supabase PostgreSQL v15.1 was discovered to contain a SQL injection vulnerability via the component /pg_meta/default/query. NOTE: the vendor's position is that this is an intended feature; also, it exists in the Supabase dashboard product,

How urgent is CVE-2024-24213?

Priority 55/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

PostgreSQL vulnerabilities

References

← Back to latest CVEs