# CVE-2026-78183: DBD::Pg version 3.21.0 for Perl has a heap out-of-bounds write in quote_float

> A heap out-of-bounds write in DBD::Pg allows attackers to cause memory corruption or execute code via crafted numeric inputs.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-6mq2-jf7v-pvjx, GHSA-785p-fw3v-r822, UBUNTU-CVE-2026-78183, openSUSE-SU-2026:11722-1

## What is CVE-2026-78183?

CVE-2026-78183 is a critical memory corruption vulnerability in perl-DBD-Pg, published on 23 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DBD::Pg version 3.21.0 for Perl has a heap out-of-bounds write in quote_float.

quote_float() allocates the length of the string + 1, which is the size of the bare numeric symbol plus NULL.  But for special literals NaN, Inf, +Inf, -Inf, Infinity, +Infinity, -Infinity it emits the literal surrounded by quotes plus NULL, which is length + 3 bytes. Every recognised literal (case-insensitive) overflows by 2 bytes, a single quote and a NULL.

This can be reached by the $dbh->quote method, for example

    $dbh->quote( "Infinity", DBI::SQL_NUMERIC ).

This regression was introduced in 3.21.0 by the quote.c rewrite.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-78183?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `perl-DBD-Pg` | openSUSE:Tumbleweed | All versions | 3.21.2-1.1 |

## How do I fix CVE-2026-78183?

Apply the vendor's patch.

## Is CVE-2026-78183 being exploited?

There is no known exploitation of CVE-2026-78183 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-78183 and fix it if it is affected.

What it is: CVE-2026-78183 is a critical memory corruption vulnerability in perl-DBD-Pg, published on 23 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-78183 in the wild and no public exploit code.

Affected product: perl-DBD-Pg. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-78183/ (Markdown: https://insights.sbomify.com/CVE-2026-78183/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-78183
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-78183
- OSV: https://osv.dev/vulnerability/CVE-2026-78183

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-78183/
Summaries are generated and may contain mistakes; the official description above is the record.