CVE-2006-2314

NONECVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 3%CVSS: —Exploit: NoneExposed: 0

A fix is available — apply it.

PostgreSQL 8.1.x before 8.1.4, 8.0.x before 8.0.8, 7.4.x before 7.4.13, 7.3.x before 7.3.15, and earlier versions allows context-dependent attackers to bypass SQL injection protection methods in applications that use multibyte encodings that allow the "\" (backslash) byte 0x5c to be the trailing byte of a multibyte character, such as SJIS, BIG5, GBK, GB18030, and UHC, which cannot be handled correctly by a client that does not understand multibyte encodings, aka a second variant of "Encoding-Based SQL Injection." NOTE: it could be argued that this is a class of issue related to interaction errors between the client and PostgreSQL, but a CVE has been assigned since PostgreSQL is treating this as a preventative measure against this class of problem.

CVSS v3
—
EG Score
0.0(none)
EPSS
84.8%
KEV
Not listed

Published

May 24, 2006

Last Modified

April 16, 2026

References (68)

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibpq-dev (8.1.4-0ubuntu1) @ dapper2026-05-31ubuntu
ubuntudovecot-common (0.99.13-3ubuntu0.1) @ hoary2026-05-31ubuntu
ubuntupython2.4-psycopg () @ breezy2026-05-31ubuntu
redhatpostgresql-0:7.4.13-2.RHEL4.12006-05-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-13 22:25 UTCEPSS rescore
  2. 2026-07-11 08:22 UTCEPSS rescore
  3. 2026-07-09 19:03 UTCEPSS rescore
  4. 2026-07-08 22:15 UTCOSV refresh
  5. 2026-07-08 15:09 UTCEPSS rescore
  6. 2026-07-06 02:19 UTCEPSS rescore
  7. 2026-07-06 02:19 UTCEPSS rescore
  8. 2026-07-04 06:26 UTCEPSS rescore
  9. 2026-07-02 14:00 UTCEPSS rescore
  10. 2026-07-01 15:01 UTCEPSS rescore
  11. 2026-06-29 14:02 UTCEPSS rescore
  12. 2026-06-29 14:02 UTCEPSS rescore
  13. 2026-06-27 03:04 UTCEPSS rescore
  14. 2026-06-25 13:46 UTCEPSS rescore
  15. 2026-06-24 14:01 UTCEPSS rescore
  16. 2026-06-24 14:01 UTCEPSS rescore
  17. 2026-06-23 21:29 UTCEPSS rescore
  18. 2026-06-23 21:29 UTCEPSS rescore
  19. 2026-06-22 14:22 UTCEPSS rescore
  20. 2026-06-21 01:56 UTCEPSS rescore
  21. 2026-06-20 10:12 UTCOSV refresh
  22. 2026-06-19 19:22 UTCEPSS rescore
  23. 2026-06-19 19:22 UTCEPSS rescore
  24. 2026-06-18 17:49 UTCEPSS rescore
  25. 2026-06-18 17:49 UTCEPSS rescore
Show 51 more
  1. 2026-06-17 17:49 UTCEPSS rescore
  2. 2026-06-17 17:49 UTCEPSS rescore
  3. 2026-06-16 17:49 UTCEPSS rescore
  4. 2026-06-16 17:49 UTCEPSS rescore
  5. 2026-06-15 17:44 UTCEPSS rescore
  6. 2026-06-14 23:13 UTCEPSS rescore
  7. 2026-06-13 22:56 UTCEPSS rescore
  8. 2026-06-12 23:08 UTCEPSS rescore
  9. 2026-06-11 13:55 UTCEPSS rescore
  10. 2026-06-10 22:14 UTCEPSS rescore
  11. 2026-06-10 13:17 UTCEPSS rescore
  12. 2026-06-07 15:21 UTCEPSS rescore
  13. 2026-06-06 13:44 UTCEPSS rescore
  14. 2026-06-06 13:44 UTCEPSS rescore
  15. 2026-06-05 22:43 UTCEPSS rescore
  16. 2026-06-05 06:07 UTCEPSS rescore
  17. 2026-06-05 06:07 UTCEPSS rescore
  18. 2026-06-04 13:09 UTCEPSS rescore
  19. 2026-06-04 13:09 UTCEPSS rescore
  20. 2026-06-02 20:10 UTCEPSS rescore
  21. 2026-06-02 20:10 UTCEPSS rescore
  22. 2026-06-01 13:49 UTCEPSS rescore
  23. 2026-06-01 13:49 UTCEPSS rescore
  24. 2026-06-01 13:49 UTCEPSS rescore
  25. 2026-05-31 22:28 UTCEPSS rescore
  26. 2026-05-31 08:30 UTCEG score recompute
  27. 2026-05-31 08:30 UTCVendor advisory
  28. 2026-05-31 08:30 UTCGHSA enrichment
  29. 2026-05-31 00:13 UTCEPSS rescore
  30. 2026-05-31 00:13 UTCEPSS rescore
  31. 2026-05-31 00:13 UTCEPSS rescore
  32. 2026-05-30 15:23 UTCOSV refresh
  33. 2026-05-29 13:40 UTCEPSS rescore
  34. 2026-05-28 13:42 UTCEPSS rescore
  35. 2026-05-28 13:42 UTCEPSS rescore
  36. 2026-05-27 13:37 UTCEPSS rescore
  37. 2026-05-27 13:37 UTCEPSS rescore
  38. 2026-05-26 13:41 UTCEPSS rescore
  39. 2026-05-26 13:41 UTCEPSS rescore
  40. 2026-05-26 07:16 UTCEPSS rescore
  41. 2026-05-26 07:16 UTCEPSS rescore
  42. 2026-05-24 16:42 UTCEPSS rescore
  43. 2026-05-22 21:15 UTCEPSS rescore
  44. 2026-05-22 21:15 UTCEPSS rescore
  45. 2026-05-21 22:38 UTCEPSS rescore
  46. 2026-05-20 22:36 UTCEPSS rescore
  47. 2026-05-20 22:36 UTCEPSS rescore
  48. 2026-05-20 11:20 UTCEPSS rescore
  49. 2026-05-20 11:20 UTCEPSS rescore
  50. 2026-05-19 21:33 UTCOSV refresh
  51. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(4)

What is CVE-2006-2314?
CVE-2006-2314 is a none vulnerability published on May 24, 2006. PostgreSQL 8.1.x before 8.1.4, 8.0.x before 8.0.8, 7.4.x before 7.4.13, 7.3.x before 7.3.15, and earlier versions allows context-dependent attackers to bypass SQL injection protection methods in applications that use multibyte encodings that allow the "\" (backslash) byte 0x5c to be the trailing…
When was CVE-2006-2314 disclosed?
CVE-2006-2314 was first published in the National Vulnerability Database on May 24, 2006, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2006-2314 actively exploited?
CVE-2006-2314 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 84.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2006-2314?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2006-2314, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2006-2314

Explore →

Is Your Infrastructure Affected by CVE-2006-2314?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs