CVE-2001-1369: Leon J Breedt pam-pgsql before 0.5.2 allows remote attackers to execute arbitrary SQL code and bypass authenti

This month

HIGH 7.5DOWNGRADE

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

Leon J Breedt pam-pgsql before 0.5.2 allows remote attackers to execute arbitrary SQL code and bypass authentication or modify user account records by injecting SQL statements into user or password fields.

Why this priority

High severity

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

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	1.6% (top 24%)
CISA exploited list	No
Published	2001-09-10
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: leon j breedt

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

Am I affected?

Timeline

2001-09-10 04:00 UTCPublished CVE record published
2026-06-16 21:56 UTCUpdated Record last modified

leon j breedt pam-pgsql DOWNGRADE

Affected: 0.5.1 · 0.5.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.5.1

1. Check installed version

apt-cache policy pam-pgsql || rpm -q pam-pgsql || pam-pgsql --version

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

apt-cache madison pam-pgsql sudo apt install pam-pgsql=<VERSION_BEFORE_0.5.1> sudo apt-mark hold pam-pgsql

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

dnf --showduplicates list pam-pgsql sudo dnf downgrade pam-pgsql-<VERSION_BEFORE_0.5.1> sudo dnf versionlock add pam-pgsql

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-2001-1369?

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

Is CVE-2001-1369 being exploited?

CVE-2001-1369 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-2001-1369 affect?

CVE-2001-1369 affects pam-pgsql. Severity is high (CVSS 7.5). Leon J Breedt pam-pgsql before 0.5.2 allows remote attackers to execute arbitrary SQL code and bypass authentication or modify user account records by injecting SQL statements into user or password fields.

How urgent is CVE-2001-1369?

Priority 45/100. High severity

Related CVEs

CVE-2004-0366 HIGH 7.5 UPGRADE SQL injection vulnerability in the libpam-pgsql library before 0.5.2 allows attackers to execute arbitrary SQL
CVE-2003-0672 HIGH 7.5 DOWNGRADE Format string vulnerability in pam-pgsql 0.5.2 and earlier allows remote attackers to execute arbitrary code v

References

← Back to latest CVEs