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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-3gjw-f78c-vvpw?

O3 pinpoints whether GHSA-3gjw-f78c-vvpw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

GHSA-3gjw-f78c-vvpw

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

GHSA-3gjw-f78c-vvpw is a security vulnerability in tokio-postgres. O3 Security confirms whether GHSA-3gjw-f78c-vvpw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

tokio-postgres: Panic on a `DataRow` with fewer fields than columns allows denial of service

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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-3gjw-f78c-vvpw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-3gjw-f78c-vvpw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-3gjw-f78c-vvpw across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works