Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2022-32406: GtkRadiant v1.6.6 was discovered to contain a buffer overflow via the component q3map2

36
Routine
MEDIUM 5.5DOWNGRADE

CVE-2022-32406 is a medium-severity flaw (CVSS 5.5) affecting gtkradiant. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

GtkRadiant v1.6.6 was discovered to contain a buffer overflow via the component q3map2. This vulnerability can cause a Denial of Service (DoS) via a crafted MAP file.

Why this priority

  • Public exploit reference

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

Risk facts

CVSS score5.5 (Medium)
Attack vectorLocal
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance0.5% (top 54%)
CISA exploited listNo
WeaknessCWE-120
Published2022-07-14
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: gtkradiant project

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

gtkradiant project gtkradiant DOWNGRADE
Affected: 1.6.6
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.6.6
1. Check installed version
apt-cache policy gtkradiant || rpm -q gtkradiant || gtkradiant --version
2. No fixed release: DOWNGRADE to a release before 1.6.6 (Debian / Ubuntu)
apt-cache madison gtkradiant sudo apt install gtkradiant=<VERSION_BEFORE_1.6.6> sudo apt-mark hold gtkradiant
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list gtkradiant sudo dnf downgrade gtkradiant-<VERSION_BEFORE_1.6.6> sudo dnf versionlock add gtkradiant
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-2022-32406?

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

Is CVE-2022-32406 being exploited?

CVE-2022-32406 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-2022-32406 affect?

CVE-2022-32406 affects gtkradiant. Severity is medium (CVSS 5.5). GtkRadiant v1.6.6 was discovered to contain a buffer overflow via the component q3map2. This vulnerability can cause a Denial of Service (DoS) via a crafted MAP file.

How urgent is CVE-2022-32406?

Priority 36/100. Public exploit reference

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.