# What is CVE-2006-3469? > CVE-2006-3469 is a medium-severity flaw (CVSS 4.0) in MySQL, published on 21 July 2006. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 29%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2006-3469 ## At a glance - **Verdict:** Fix this soon. Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month. - **Precursor Intelligence risk score:** 32 out of 100 (Low); action: Monitor. Kept up to date as the evidence changes. - **Severity:** Medium (CVSS 4.0 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 29% (latest exploit-likelihood forecast) - **Published:** 21 July 2006 - **Record last updated:** 16 June 2026 - **Main product:** MySQL - **Affected products:** 2 ## What is CVE-2006-3469? In plain terms It can be attacked from anywhere on the internet with one login. If it works, the attacker can slow it down. ### The official description Format string vulnerability in time.cc in MySQL Server 4.1 before 4.1.21 and 5.0 before 1 April 2006 allows remote authenticated users to cause a denial of service (crash) via a format string instead of a date as the first parameter to the date_format function, which is later used in a formatted print call to display the error message. ### What kind of flaw is it? - CWE-134: Use of Externally-Controlled Format String ### How an attack on it works - Where an attacker can be: Anywhere on the internet - How hard it is to pull off: Easy: no special conditions - Login needed first: One login - What an attacker gets: Can slow it down Severity vector: `AV:N/AC:L/Au:S/C:N/I:N/A:P` ## Is CVE-2006-3469 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 29%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 29%, 29%, 29%, 29%, 29%, 29%, 29%. ### Timeline - 21 July 2006: Published - 31 July 2025: Exploit likelihood fell - 2 October 2025: Exploit likelihood jumped - 16 June 2026: Record last updated ### How Precursor Intelligence ranks it CVE-2006-3469 scores **32 out of 100 (Low)**, with the action "Monitor". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: smaller factor - Threat activity around it: smaller factor 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2006-3469? The published record lists 2 products. - [MySQL](https://www.precursorintelligence.com/product/mysql/mysql) by [MySQL](https://www.precursorintelligence.com/vendors/mysql) (Application): 4.1.8, 4.1.12, 4.1.13, 4.1.14, 4.1.15, 5.0.5.0.21, 5.0.10, 5.0.15, 5.0.16, 5.0.17 - [MySQL](https://www.precursorintelligence.com/product/oracle/mysql) by [Oracle](https://www.precursorintelligence.com/vendors/oracle) (Application): 4.1.6, 4.1.7, 4.1.9, 4.1.11, 4.1.16, 4.1.18, 4.1.19, 4.1.20, 5.0.6, 5.0.9, 5.0.11, 5.0.12, 5.0.13, 5.0.18, 5.0.19 ## How do I fix CVE-2006-3469? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [debian.org](http://www.debian.org/security/2006/dsa-1112) (Patch, Vendor advisory) - [secunia.com](http://secunia.com/advisories/21147) (Vendor advisory) - [secunia.com](http://secunia.com/advisories/21366) (Vendor advisory) - [secunia.com](http://secunia.com/advisories/24479) (Vendor advisory) - [secunia.com](http://secunia.com/advisories/31226) (Vendor advisory) - [vupen.com](http://www.vupen.com/english/advisories/2007/0930) (Vendor advisory) - [bugs.debian.org](http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375694) - [bugs.mysql.com](http://bugs.mysql.com/bug.php?id=20729) - [dev.mysql.com](http://dev.mysql.com/doc/refman/4.1/en/news-4-1-21.html) - [docs.info.apple.com](http://docs.info.apple.com/article.html?artnum=305214) - [lists.apple.com](http://lists.apple.com/archives/security-announce/2007/Mar/msg00002.html) - [security.gentoo.org](http://security.gentoo.org/glsa/glsa-200608-09.xml) - [redhat.com](http://www.redhat.com/support/errata/RHSA-2008-0768.html) - [securityfocus.com](http://www.securityfocus.com/bid/19032) - [ubuntu.com](http://www.ubuntu.com/usn/usn-321-1) - [us-cert.gov](http://www.us-cert.gov/cas/techalerts/TA07-072A.html) (Government resource) - [oval.cisecurity.org](https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A9827) ## Questions ### What is CVE-2006-3469? CVE-2006-3469 is a medium-severity flaw in MySQL, published on 21 July 2006. It can be attacked from anywhere on the internet with one login. If it works, the attacker can slow it down. ### How serious is CVE-2006-3469? It scores 4.0 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2006-3469 is 32 out of 100, which is Low. Its action is "Monitor". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month. ### Is CVE-2006-3469 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 29%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2006-3469 affect? For MySQL: 4.1.8, 4.1.12, 4.1.13, 4.1.14, 4.1.15, 5.0.5.0.21 and 4 more. The record lists 2 products in all, each with its versions, under "Who is affected" on this page. ### How do I fix CVE-2006-3469? Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2006-3469 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact