# GHSA-3gjw-f78c-vvpw: Panic on a `DataRow` with fewer fields than columns allows denial of service

> A malicious server can cause a denial of service by sending malformed data rows, crashing the Rust database client application.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Jun 2026
- **Also known as:** RUSTSEC-2026-0178

## What is GHSA-3gjw-f78c-vvpw?

GHSA-3gjw-f78c-vvpw is a denial of service vulnerability in tokio-postgres, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A malicious or compromised server can send a row containing fewer fields than
its row description declares columns. Reading one of the missing columns then
panics with an out-of-bounds index, aborting the calling task. This affects even
the otherwise non-panicking `try_get`, and both `Row` and `SimpleQueryRow`.

Applications that connect only to a trusted database are not exposed; the risk
applies to clients that may connect to untrusted or user-supplied servers, or
whose connection can be intercepted by a man-in-the-middle.

## Which versions are affected by GHSA-3gjw-f78c-vvpw?

3 open source packages ship an affected version, including tokio-postgres.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tokio-postgres` | crates.io | From 0.4.0 | 0.7.18 |
| `tokio-postgres` | crates.io | From 0.4.0 | 0.7.18 |
| `tokio-postgres` | crates.io | From 0.4.0 | 0.7.18 |

## How do I fix GHSA-3gjw-f78c-vvpw?

Upgrade tokio-postgres to 0.7.18 or later.

## Is GHSA-3gjw-f78c-vvpw being exploited?

There is no known exploitation of GHSA-3gjw-f78c-vvpw in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-3gjw-f78c-vvpw and fix it if it is affected.

What it is: GHSA-3gjw-f78c-vvpw is a denial of service vulnerability in tokio-postgres, published on 12 Jun 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 GHSA-3gjw-f78c-vvpw in the wild and no public exploit code.

Affected packages and fixed versions:
- tokio-postgres (crates.io): affected from 0.4.0; fixed in 0.7.18
- tokio-postgres (crates.io): affected from 0.4.0; fixed in 0.7.18
- tokio-postgres (crates.io): affected from 0.4.0; fixed in 0.7.18

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/GHSA-3gjw-f78c-vvpw/ (Markdown: https://insights.sbomify.com/GHSA-3gjw-f78c-vvpw/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-3gjw-f78c-vvpw

---
From sbomify Insights: https://insights.sbomify.com/GHSA-3gjw-f78c-vvpw/
Summaries are generated and may contain mistakes; the official description above is the record.