How severe is GHSA-3gjw-f78c-vvpw?

No CVSS score has been assigned to GHSA-3gjw-f78c-vvpw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3gjw-f78c-vvpw?

GHSA-3gjw-f78c-vvpw affects the following packages: tokio-postgres (crates.io). Ecosystems affected: crates.io.

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

Update tokio-postgres to 0.7.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3gjw-f78c-vvpw is resolved across your whole dependency graph.

How do I detect GHSA-3gjw-f78c-vvpw in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tokio-postgres, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-3gjw-f78c-vvpw if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-3gjw-f78c-vvpw actively exploited in the wild?

No public exploit code has been indexed for GHSA-3gjw-f78c-vvpw yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-3gjw-f78c-vvpw published, and has it been updated?

GHSA-3gjw-f78c-vvpw was published on August 24, 2026 and was last updated on August 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

tokio-postgres: Panic on a `DataRow` with fewer fields than columns allows denial of serviceGHSA-3gjw-f78c-vvpw

Fix: rust-postgres/rust-postgres@7a00ffa

GHSA-3gjw-f78c-vvpw is a security vulnerability in tokio-postgres. A fix is available for tokio-postgres — see the affected versions and patch details below.

Also known asRUSTSEC-2026-0178

Published

Aug 24, 2026

Updated

Aug 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 25, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀tokio-postgres

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`tokio-postgres`	≥ 0.4.0&&< 0.7.18	0.7.18`cargo update -p tokio-postgres --precise 0.7.18`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tokio-postgres, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tokio-postgres to 0.7.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3gjw-f78c-vvpw is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-3gjw-f78c-vvpw in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works