How severe is CVE-2006-4181?

CVE-2006-4181 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2006-4181 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 5% (91st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2006-4181?

CVE-2006-4181 primarily affects Gnu Radius. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2006-4181?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2006-4181 published?

CVE-2006-4181 was published on 2006-11-28 and last updated on 2026-06-16.

CVE-2006-4181

CVE-2006-4181 is a critical-severity vulnerability in Gnu Radius with a CVSS 2.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 5% (91st percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Gnu Radius
Published: 2006-11-28
Last modified: 2026-06-16

Description

Format string vulnerability in the sqllog function in the SQL accounting code for radiusd in GNU Radius 1.2 and 1.3 allows remote attackers to execute arbitrary code via unknown vectors.

Frequently asked questions

What is CVE-2006-4181?: Format string vulnerability in the sqllog function in the SQL accounting code for radiusd in GNU Radius 1.2 and 1.3 allows remote attackers to execute arbitrary code via unknown vectors.
How severe is CVE-2006-4181?: CVE-2006-4181 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2006-4181 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 5% (91st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2006-4181?: CVE-2006-4181 primarily affects Gnu Radius. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2006-4181?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2006-4181 published?: CVE-2006-4181 was published on 2006-11-28 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:gnu:radius:1.2:*:*:*:*:*:*:*
cpe:2.3:a:gnu:radius:1.3:*:*:*:*:*:*:*

More vulnerabilities in Gnu Radius

CVE-2001-1376 — High (CVSS 7.5): Buffer overflow in digest calculation function of multiple RADIUS implementations allows remote attackers to cause a…
CVE-2004-0849 — Medium (CVSS 5.0): Integer overflow in the asn_decode_string() function defined in asn1.c in radiusd for GNU Radius 1.1 and 1.2 before…
CVE-2004-0576 — Medium (CVSS 5.0): The radius daemon (radiusd) for GNU Radius 1.1, when compiled with the -enable-snmp option, allows remote attackers to…
CVE-2004-0131 — Medium (CVSS 5.0): The rad_print_request function in logger.c for GNU Radius daemon (radiusd) before 1.2 allows remote attackers to cause…
CVE-2001-1377 — Medium (CVSS 5.0): Multiple RADIUS implementations do not properly validate the Vendor-Length of the Vendor-Specific attribute, which…

All CVEs affecting Gnu Radius →