CVE-2005-2626: Unspecified vulnerability in Kismet before 2005-08-R1 allows remote attackers to have an unknown impact via un

This month

HIGH 10.0DOWNGRADE

CVE-2005-2626 is a high-severity flaw (CVSS 10.0) affecting kismet. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Unspecified vulnerability in Kismet before 2005-08-R1 allows remote attackers to have an unknown impact via unprintable characters in the SSID.

Why this priority

Critical severity

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

Risk facts

CVSS score	10.0 (High)
EPSS exploit chance	3.7% (top 10%)
CISA exploited list	No
Published	2005-08-19
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: kismet

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

Am I affected?

Timeline

2005-08-19 04:00 UTCPublished CVE record published
2026-06-16 22:15 UTCUpdated Record last modified

kismet kismet DOWNGRADE

Affected: 2.4.5 · 2.4.6 · 2.6.0 · 2.8.0 · 2.8.0a · 2.8.1 · 2004-02_r1 · 2004-04_r1

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.4.5

1. Check installed version

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

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

apt-cache madison kismet sudo apt install kismet=<VERSION_BEFORE_2.4.5> sudo apt-mark hold kismet

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

dnf --showduplicates list kismet sudo dnf downgrade kismet-<VERSION_BEFORE_2.4.5> sudo dnf versionlock add kismet

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-2005-2626?

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

Is CVE-2005-2626 being exploited?

CVE-2005-2626 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-2005-2626 affect?

CVE-2005-2626 affects kismet. Severity is high (CVSS 10.0). Unspecified vulnerability in Kismet before 2005-08-R1 allows remote attackers to have an unknown impact via unprintable characters in the SSID.

How urgent is CVE-2005-2626?

Priority 57/100. Critical severity

Related CVEs

CVE-2005-2627 HIGH 7.5 DOWNGRADE Multiple integer underflows in Kismet before 2005-08-R1 allow remote attackers to execute arbitrary code via (
CVE-2002-0904 HIGH 7.5 DOWNGRADE SayText function in Kismet 2.2.1 and earlier allows remote attackers to execute arbitrary commands via shell m

References

← Back to latest CVEs