CVE-2002-0802

7.5 HIGH 1% exploit odds No fix listed

What it is

The multibyte support in PostgreSQL 6.5.x with SQL_ASCII encoding consumes an extra character when processing a character that cannot be converted, which could remove an escape character from the query and make the application subject to SQL injection attacks.

At a glance

Exploitability: Can be exploited over the network without logging in. Limited direct impact.
Exploit odds: 1.1% chance of exploitation in the next 30 days (EPSS).
Fix: No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

2002-08-12 04:00 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-06-16 21:58 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 1.1% in the next 30 days (EPSS).
Severity: 7.5 HIGH (CVSS).
Fix: none linked yet, which raises it.

Details

Published: 2002-08-12 04:00 UTC
Last modified: 2026-06-16 21:58 UTC
Exploit probability: 1.1% · EPSS, next 30 days
Record status: Modified

Affected

PostgreSQL 6.5.0

Attack profile CVSS 2.0 · 7.5

Attack vector: Network
Complexity: Low
Authentication: None
Confidentiality: Partial
Integrity: Partial
Availability: Partial

Raw vector

AV:N/AC:L/Au:N/C:P/I:P/A:P

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2002-0802.md and follow it. Check whether this project is affected by CVE-2002-0802. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

References

NVD record · CVE.org record