CVE-2006-5932: Kahua before 0.7, when running multiple applications under a single supervisor, grants application access on t

This month

HIGH 7.5DOWNGRADE

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

Kahua before 0.7, when running multiple applications under a single supervisor, grants application access on the basis of username instead of username and database name, which allows remote authenticated users to obtain unauthorized access if different databases assign the same username to different user accounts.

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.7% (top 23%)
CISA exploited list	No
Published	2006-11-16
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: kahua

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

Am I affected?

Timeline

2006-11-16 00:07 UTCPublished CVE record published
2026-06-16 22:32 UTCUpdated Record last modified

kahua kahua DOWNGRADE

Affected: 0.1 · 0.2 · 0.3 · 0.4 · 0.5 · 0.6

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.1

1. Check installed version

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

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

apt-cache madison kahua sudo apt install kahua=<VERSION_BEFORE_0.1> sudo apt-mark hold kahua

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

dnf --showduplicates list kahua sudo dnf downgrade kahua-<VERSION_BEFORE_0.1> sudo dnf versionlock add kahua

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-2006-5932?

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

Is CVE-2006-5932 being exploited?

CVE-2006-5932 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-2006-5932 affect?

CVE-2006-5932 affects kahua. Severity is high (CVSS 7.5). Kahua before 0.7, when running multiple applications under a single supervisor, grants application access on the basis of username instead of username and database name, which allows remote authenticated users to obtain unauthorized access

How urgent is CVE-2006-5932?

Priority 45/100. High severity

References

← Back to latest CVEs