Vulnerability Database · AlmaLinux · Package report

pg_repack: vulnerability history, versions and safety

pg_repack is a package in the AlmaLinux ecosystem. Vulert records 50 vulnerabilities for it across 10 affected ranges, from Nov 2021 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
50 vulnerabilities recorded U50
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
16 in the last 12 months

Most recent disclosure 28 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on pg_repack i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 28 Sep 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 50 vulnerabilities on record across 4 years, 16 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 50 over 4 years · 16 in the last year i
  • Latest disclosure 28 Sep 2026 i
  • Highest CVSS n/a i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
up to 1.5.1-1.module_el8.10.0+4199+bf03c564 (exclusive) 2
up to 1.5.1-1.module_el8.10.0+3930+ecf33554 (exclusive) 5
up to 1.4.8-1.module_el8.10.0+3798+606ebb9f (exclusive) 1
up to 1.4.8-1.module_el8.9.0+3706+885c732e (exclusive) 8
up to 1.4.8-1.module_el8.8.0+3487+43ec1b9f (exclusive) 3
up to 1.4.6-3.module_el8.9.0+3704+f1f917ce (exclusive) 8
up to 1.4.6-3.module_el8.6.0+3094+eb237fb8 (exclusive) 1
up to 1.4.6-3.module_el8.6.0+2760+1746ec94 (exclusive) 13
up to 1.4.6-3.module_el8.6.0+2758+4f4474df (exclusive) 7
up to 1.4.6-3.module_el8.5.0+2606+4554acc4 (exclusive) 2

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 4
  • 2022 4
  • 2023 7
  • 2024 11
  • 2025 8
  • 2026 16

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 16 of the 50 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for pg_repack

The 5 most severe of 50 vulnerabilities recorded for this package

Search all 50 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Security Update for PostgreSQL: Addressing Timing Channel and Integer Overflow Vulnerabilities N/A unrated 1.4.8-1.module_el8.9.0+3706+885c732e 16 Jun 2026
Critical Security Update for PostgreSQL:15 - Arbitrary Code Execution Vulnerability N/A unrated 1.4.8-1.module_el8.9.0+3706+885c732e 02 Sep 2025
Important: postgresql:16 security update N/A unrated 1.4.8-1.module_el8.10.0+3798+606ebb9f 28 Aug 2024
Critical Vulnerability in PostgreSQL: Code Execution Risks in Restore Operations N/A unrated 1.4.6-3.module_el8.6.0+2760+1746ec94 02 Sep 2025
Critical Security Update for PostgreSQL: Addressing Code Execution Vulnerabilities N/A unrated 1.4.6-3.module_el8.9.0+3704+f1f917ce 28 Sep 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About pg_repack

Is pg_repack safe to use?

Vulert records 50 vulnerabilities for pg_repack in AlmaLinux: 0 critical, 0 high, 0 medium and 0 low, plus 50 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does pg_repack have?

50 vulnerabilities are recorded for pg_repack in the AlmaLinux ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 50 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new pg_repack vulnerabilities disclosed?

16 vulnerabilities were recorded for pg_repack in the last 12 months, and the oldest entry in this database dates to 09 Nov 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of pg_repack are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor pg_repack for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the pg_repack version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.