CVE-2024-1713: A user who can create objects in a database with plv8 3.2.1 installed is able to cause deferred triggers to ex

This month

HIGH 7.2DOWNGRADE

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

A user who can create objects in a database with plv8 3.2.1 installed is able to cause deferred triggers to execute as the Superuser during autovacuum.

Why this priority

High severity
Public exploit reference

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

Risk facts

CVSS score	7.2 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	High
User interaction	None
EPSS exploit chance	0.6% (top 54%)
CISA exploited list	No
Weakness	CWE-394, CWE-754
Published	2024-03-14
Last modified	2026-06-17

Publisher (CNA): Google Inc. · Vendor: plv8

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

Am I affected?

Timeline

2024-03-14 21:15 UTCPublished CVE record published
2026-06-17 07:04 UTCUpdated Record last modified

plv8 plv8 DOWNGRADE

Affected: 3.2.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.2.1

1. Check installed version

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

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

apt-cache madison plv8 sudo apt install plv8=<VERSION_BEFORE_3.2.1> sudo apt-mark hold plv8

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

dnf --showduplicates list plv8 sudo dnf downgrade plv8-<VERSION_BEFORE_3.2.1> sudo dnf versionlock add plv8

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

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

Is CVE-2024-1713 being exploited?

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

CVE-2024-1713 affects plv8. Severity is high (CVSS 7.2). A user who can create objects in a database with plv8 3.2.1 installed is able to cause deferred triggers to execute as the Superuser during autovacuum.

How urgent is CVE-2024-1713?

Priority 42/100. High severity; Public exploit reference

References

← Back to latest CVEs